/krx/companies/treasury-stock

POST /api/krx/companies/treasury-stock

Price: 5 credits

List treasury-stock acquisition and disposal reports of Korea Exchange companies from KRX KIND, newest first, by report window, market, holding method and action: report date, company, method, action, trading period, declared shares and the executed shares, ratio and amount to date

How to use it

Use krx/disclosures/search with report_name for the underlying filings.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• date_from integer nullable — Earliest report day, unix seconds (UTC day); defaults to 90 days before date_to
• date_to integer nullable — Latest report day, unix seconds (UTC day); defaults to today in Korea
• market string — Market (default: "all"; one of: "all", "kospi", "kosdaq", "konex")
• method string — How the shares are held (default: "all"; one of: "all", "direct", "stock_option", "trust")
• action string — Acquisition or disposal (default: "all"; one of: "all", "acquisition", "disposal")
• count integer required — Max number of results (min: 1; max: 1000)

Response

• @type string (default: "KrxTreasuryStockFiling")
• reported_at integer nullable
• company_id string nullable
• company_name string nullable
• market string nullable
• badges array (default: [])
• method string nullable
• action string nullable
• period_start integer nullable
• period_end integer nullable
• declared_shares number nullable
• executed_shares number nullable
• executed_ratio number nullable
• executed_amount number nullable

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 — The entity was not found, or a precondition failed 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.