/bse/ipo-projects/search

POST /api/bse/ipo-projects/search

Price: 1 credit

Search the IPO applications reviewed by the Beijing Stock Exchange, by company or intermediary name and review status: company, NEEQ stock code, status code, registered address, sponsor, law firm, accounting firm and appraiser with their signing staff, and the receipt and update dates

How to use it

Most recently updated first. `keyword` matches intermediaries too. Pass `id` to bse/ipo-projects for the review dates and disclosed documents.

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 IPO projects to return (min: 1; max: 1000)
• keyword string nullable — Company or intermediary name to match (examples: "中信建投", "科技"; minLength: 1)
• status_codes array nullable — Review status codes to keep (examples: ["P02"], ["P07-1","P07-2"]; minItems: 1)

Response

• @type string (default: "BseIpoProject")
• id string required
• item_number string nullable
• company_name string nullable
• stock_code string nullable
• stock_name string nullable
• status_code string nullable
• company_type_code string nullable
• registered_address string nullable
• sponsor string nullable
• sponsor_representatives array (default: [])
• law_firm string nullable
• lawyers array (default: [])
• accounting_firm string nullable
• accountants array (default: [])
• appraiser string nullable
• appraisers array (default: [])
• received_date integer nullable
• published_date integer nullable
• operated_at integer nullable
• updated_at integer nullable

Errors

• 422 — A status code is not shaped like P02 or P07-1 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.