/krx/ipos/search

POST /api/krx/ipos/search

Price: 5 credits

List the Korea Exchange IPO pipeline from KRX KIND by window: public offerings in progress (filing, demand forecast, subscription and payment dates, offer price and amount, scheduled listing), pre-listing reviews (application, decision and result) and new listings (date, type, security type, industry, country), with the company, market and lead underwriter

How to use it

Use krx/companies/search to resolve a newly listed company's ticker.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• kind string required — IPO pipeline list (one of: "offerings", "listing_reviews", "new_listings")
• date_from integer nullable — Earliest day, unix seconds (UTC day); defaults to 180 days before date_to
• date_to integer nullable — Latest day, unix seconds (UTC day); defaults to today in Korea
• count integer required — Max number of results (min: 1; max: 300)

Response

• @type string (default: "KrxIpo")
• id string nullable
• kind string required
• company_id string nullable
• company_name string required
• market string nullable
• badges array (default: [])
• filed_at integer nullable
• demand_forecast_start integer nullable
• demand_forecast_end integer nullable
• subscription_start integer nullable
• subscription_end integer nullable
• payment_at integer nullable
• offer_price number nullable
• offer_amount_krw_millions number nullable
• listing_at integer nullable
• listing_type string nullable
• security_type string nullable
• industry string nullable
• country string nullable
• applied_at integer nullable
• decided_at integer nullable
• review_result string nullable
• underwriter string 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.