/dart/filings

POST /api/dart/filings

Price: 40 credits

Get a filing from DART, the Korean FSS disclosure system, by receipt number: company, report name, filing date, the table of contents of the main document with a viewer link per section, attachments, amended versions, previous periodic reports, and optionally the text of every top-level section

How to use it

Receipt numbers come from dart/filings/search and dart/filings/recent. A top-level section's text includes its sub-sections.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — DART receipt number or filing viewer URL (examples: "20260814003699", "https://dart.fss.or.kr/dsaf001/main.do?rcpNo=20261002901116")
• include_text boolean — Fetch the text of every top-level section of the main document (default: false)

Response

• @type string (default: "DartFilingDetail")
• id string required
• url string required
• company_name string nullable
• report_name string nullable
• filed_at integer nullable
• document_id string nullable
• sections array (default: [])
  • @type string (default: "DartFilingSection")
  • id string required
  • level integer required
  • url string required
  • length integer nullable
  • text string nullable
• attachments array (default: [])
  • @type string (default: "DartFilingDocument")
  • id string required
  • receipt_id string nullable
  • filed_at integer nullable
• versions array (default: [])
  • @type string (default: "DartFilingDocument")
  • id string required
  • receipt_id string nullable
  • filed_at integer nullable
• previous_reports array (default: [])
  • @type string (default: "DartFilingDocument")
  • id string required
  • receipt_id string nullable
  • filed_at integer nullable

Errors

• 422 — id is not a receipt number Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No DART filing under that receipt number Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.