/bse/public-offerings/search

POST /api/bse/public-offerings/search

Price: 5 credits

List the public share offerings on the Beijing Stock Exchange, in progress or completed: issue code and price, P/E, shares offered, and the plan, notice, roadshow, subscription, result and listing dates

How to use it

Latest subscription date first. `initial_issue_shares` counts shares before any over-allotment.

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 offerings to return (min: 1; max: 500)
• stage string nullable — Offering stage; both when omitted (one of: "issuing", "completed")
• keyword string nullable — Stock code or name to match (examples: "南方乳业", "874142"; minLength: 1)

Response

• @type string (default: "BsePublicOffering")
• id string required
• item_number string nullable
• stock_code string nullable
• stock_name string nullable
• issue_code string nullable
• issue_price_cny number nullable
• pe_ratio number nullable
• initial_issue_shares integer nullable
• pricing_method_code string nullable
• company_type_code string nullable
• plan_date integer nullable
• issue_notice_date integer nullable
• enquiry_notice_date integer nullable
• enquiry_start_date integer nullable
• enquiry_end_date integer nullable
• roadshow_date integer nullable
• roadshow_start_time string nullable
• roadshow_end_time string nullable
• roadshow_url string nullable
• subscription_date integer nullable
• bidding_result_date integer nullable
• issue_result_date integer nullable
• listing_date integer nullable
• suspended_date integer nullable
• terminated_date integer nullable
• image string nullable
• report_url string nullable
• report_image string nullable
• operated_at integer nullable
• updated_at integer nullable

Errors

• 422 — An unknown stage 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.