📣 Korea DART Corporate Filing Watch

Follow new Korean corporate disclosure filings as they appear on the official DART filing list — filer, report name and filing date as listed — as a change feed keyed on the source-native rcpNo. Public, logged-out DART filing list; no API key, login, cookie or CAPTCHA.

Output is one filing_record row per result; billing is pay-per-event, the value event being one filing delta (a $0.02 start fee per run, then $0.15 per filing delta plus one $0.10 source check per run that reads the source). Source: dart.fss.or.kr.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

Who it's for

Investors and analysts tracking Korean listed companies, compliance and monitoring teams, and data teams that need a dated feed of new DART filings rather than a one-off list.

📊 Sample Output

Real rows from run nKDgaEHVChzXYgMtk on build 0.1.21 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

rcp_no	market_marker	filer	report_name	filed_date	listed_as
20260917000373	2026.09.18	삼보산업	[기재정정] 주요사항보고서(유상증자결정)	2026.09.18	코 삼보산업
20260917000375	2026.09.18	인산가	[기재정정] 주요사항보고서(유상증자결정)	2026.09.18	코 인산가
20260917000376	2026.09.18	젠큐릭스	[기재정정] 주요사항보고서(영업정지)	2026.09.18	코 젠큐릭스
20260917900669	코	코스닥시장본부	주권매매거래정지해제 (상장폐지에 따른 정리매매 개시)	2026.09.17	코 삼영이엔씨
20260917900668	코	코스닥시장본부	기타시장안내 ((주)제일엠앤에스 기업심사위원회 심의·의결 결과 안내)	2026.09.17	코 제일엠앤에스
20260917900667	코	코스닥시장본부	주권매매거래정지해제 (상장폐지에 따른 정리매매 개시)	2026.09.17	코 제일엠앤에스
20260917900665	코	코스닥시장본부	기타시장안내 (기업심사위원회 심의·의결 결과 안내)	2026.09.17	코 삼영이엔씨
20260917800659	유	롯데지주	타법인주식및출자증권취득결정 (자회사의 주요경영사항)	2026.09.17	유 롯데지주 IR

The run finished with the status message: PARTIAL: emitted 25 item(s); PREVIEW: snapshot output is capped at 25 record(s); 5 further record(s) withheld. Use watch mode for the full change feed.

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_key (string/null) — e.g. dart:20260917000373
• rcp_no — e.g. 20260917000373
• market_marker — e.g. 2026.09.18
• filer — e.g. 삼보산업
• report_name — e.g. [기재정정] 주요사항보고서(유상증자결정)
• filed_date — e.g. 2026.09.18
• listed_as — e.g. 코 삼보산업
• source_url — e.g. https://dart.fss.or.kr/dsaf001/main.do?rcpNo=20260917000373
• scope_note — e.g. list-page fields only; document contents not read
• record_type (string) — e.g. filing_record
• delta_type (string/null) — null in every sample row

What each record contains

A filing_record (snapshot) or filing-delta (watch): the filer name, report name, and filing date exactly as listed on the DART filing list, keyed on the source-native rcpNo. In watch mode each delta is NEW / CHANGED / REMOVED with before / after and changed_fields.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "max_results": 30,
  "pages": 1,
  "watch_mode": false,
  "max_items": 40
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.15 filing-delta = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
  "max_results": 5,
  "pages": 1,
  "watch_mode": false,
  "max_items": 40
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
  "max_results": 30,
  "pages": 1,
  "watch_mode": true,
  "max_items": 40
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.15 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

One real record from run nKDgaEHVChzXYgMtk, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_key": "dart:20260917000373",
  "rcp_no": "20260917000373",
  "market_marker": "2026.09.18",
  "filer": "삼보산업",
  "report_name": "[기재정정] 주요사항보고서(유상증자결정)",
  "filed_date": "2026.09.18",
  "listed_as": "코 삼보산업",
  "source_url": "https://dart.fss.or.kr/dsaf001/main.do?rcpNo=20260917000373",
  "scope_note": "list-page fields only; document contents not read",
  "record_type": "filing_record",
  "schema_version": "1.0",
  "output_mode": "preview",
  "preview_cap": 25,
  "preview_truncated": 5
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each filing delta is charged at the moment it is pushed (filing-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

First run and later runs — read this first

This Actor sells change detection, not bulk export. Two modes:

• Snapshot (watch_mode: false, the prefilled default): returns the current filing list as a preview, hard-capped at 25 records regardless of max_items. Billed one source-check only — the preview records are not billed. Use it to see the data now.
• Watch (watch_mode: true): the first run seeds a private baseline and emits zero deltas (billed one source-check). Every run after emits one delta per newly appeared filing — the value event. A run with no new filings emits zero and bills only the source-check.

Source, scope and limits

DART public filing list (dart.fss.or.kr), list-page scope only — filer, report name and filing date as listed. It does not open, parse or characterise the filing document itself. Snapshot mode is a capped preview, not a bulk export. Terminal states: NORMAL · SUCCEEDED-0: GENUINE_EMPTY · SUCCEEDED-0 (no change) · PARTIAL · BLOCKED.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Source check (source-check)	$0.10	$0.09	$0.08	$0.07
Filing Delta (filing-delta)	$0.15	$0.14	$0.12	$0.10

Worked at the live Free-tier price (watch mode, one delta per change):

• 8 filing deltas: $0.02 start + $0.10 source check + 8 × $0.15 = $1.32
• 25 filing deltas: $0.02 start + $0.10 source check + 25 × $0.15 = $3.87
• 100 filing deltas: $0.02 start + $0.10 source check + 100 × $0.15 = $15.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: PARTIAL: emitted 25 item(s); PREVIEW: snapshot output is capped at 25 record(s); 5 further record(s) withheld. Use watch mode for the full change feed.. max_results is a hard ceiling on what is delivered and billed, never a target. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by dart.fss.or.kr. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (dart.fss.or.kr) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee plus one source check.

Q: How many rows can one run return?
A: Up to max_results (default 100); snapshot previews stop at 25. Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store (baseline_id names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other market announcement watches actors?
A: Same output shape and billing model; this one covers dart.fss.or.kr. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (max_results) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
• First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

🔗 Related Actors

• ASX Announcement Event Watch — ASX company announcements per issuer: headline, announcement type and price-sensitive flag, keyed on the source-native documentKey
• 📺 Bilibili Trends Watch — Trending & Ranking Deltas — Bilibili public trending/popular/ranking watch — new and changed entries with deltas; original Chinese retained alongside translation
• GOV.UK Press Release Feed — official search API — Press releases from the official GOV.UK search API — title, department, date, link. Filter by keyword or organisation. No API key; pay per release
• 📰 Press-Release Event Feed — Official Newsroom Watch — One deduped press-release event feed from buyer-supplied official newsroom feeds, with confirmed cross-feed deltas. No licensed wires
• SGX Financial Report & Disclosure Document Watch — Singapore Exchange financial-report and disclosure documents as they are lodged: annual, interim, quarterly, business-review, sustainability and summ…
• Taiwan MOPS Material Information Watch — Taiwan listed-company material information (重大訊息) as published to the MOPS open data feed: subject, statute clause and event date, keyed on the sourc…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.