/dart/companies

POST /api/dart/companies

Price: 1 credit

Get a company from DART, the Korean FSS disclosure system, by corp code, ticker or exact name: Korean and English name, ticker, CEO, corporation class and market, corporate and business registration numbers, address, website, IR website, phone, fax, industry, founding date, fiscal year end, and the name and CEO history newest first

How to use it

An inexact name may resolve to a different company; take the corp code from dart/companies/search.

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 corp code, KRX ticker or exact company name (examples: "00126380", "005930", "삼성전자")

Response

• @type string (default: "DartCompany")
• id string required
• name string required
• name_en string nullable
• disclosure_name string nullable
• ticker string nullable
• ceo string nullable
• corporation_class string nullable
• market string nullable
• corporate_registration_number string nullable
• business_registration_number string nullable
• address string nullable
• website string nullable
• ir_website string nullable
• phone string nullable
• fax string nullable
• industry string nullable
• founded_at integer nullable
• fiscal_year_end_month integer nullable
• name_history array (default: [])
• ceo_history array (default: [])

Errors

• 422 — The request body did not validate 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 company under that corp code, ticker or name 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.