/hkexnews/new_listings/search

POST /api/hkexnews/new_listings/search

Price: 10 credits

Companies newly listed on the Main Board of the Hong Kong Exchange in a given year, from HKEX's new listing report: stock code, company name, prospectus and listing dates, sponsors, reporting accountants, valuers, funds raised and IPO price per offer tranche, and listing categories such as biotech (Chapter 18A) or weighted voting rights.

How to use it

Rows come in listing-date order, oldest first; the current year is listed up to the report's last update. Transfers from GEM carry no funds raised, with the reason in remark.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of new listings to return (min: 1)
• year integer nullable — Calendar year of listing (examples: 2025, 2019; min: 2012)

Response

• @type string (default: "HkexnewsNewListing")
• stock_code string nullable
• company_name string nullable
• listing_categories array (default: [])
• prospectus_date integer nullable
• listing_date integer nullable
• sponsors array (default: [])
• reporting_accountants array (default: [])
• valuers array (default: [])
• funds_raised number nullable
• offer_price number nullable
• tranches array (default: [])
  • @type string (default: "HkexnewsNewListingTranche")
  • label string nullable
  • funds_raised number nullable
  • offer_price number nullable
• remark string nullable
• year integer nullable
• board 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 — No new listing report for that year 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.