POST /api/hkexnews/new_listings/search
Price: 10 credits
Companies newly listed on the Main Board or GEM of the Hong Kong Exchange in a given year, from HKEX's new listing reports: stock code, company name, listing date, sponsors, reporting accountants, funds raised and offer price. Main Board rows add the prospectus date, valuers, funds raised and price per offer tranche, and listing categories such as biotech (Chapter 18A) or weighted voting rights; GEM rows add the subscription ratio, shares outstanding and market capitalisation at listing, industry, place of incorporation and the listing methods.
Rows come in listing-date order, oldest first; the current year is listed up to the report's last update. Main Board reports start in 1994 and GEM reports in 1999. Main Board transfers from GEM and listings by introduction carry no funds raised, with the reason in remark.
access-token string requiredtimeout 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: 1994)board string — Listing board (default: "main_board"; one of: "main_board", "gem")@type string (default: "HkexnewsNewListing")stock_code string nullablecompany_name string nullablelisting_categories array (default: [])prospectus_date integer nullablelisting_date integer nullablesponsors array (default: [])reporting_accountants array (default: [])valuers array (default: [])funds_raised number nullableoffer_price number nullabletranches array (default: [])@type string (default: "HkexnewsNewListingTranche")label string nullablefunds_raised number nullableoffer_price number nullablesubscription_ratio number nullableshares_outstanding integer nullablemarket_cap number nullableindustry string nullableplace_of_incorporation string nullablelisting_methods array (default: [])remark string nullableyear integer nullableboard string nullable422 — 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 and board 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.