/sse/ipo-projects/search

POST /api/sse/ipo-projects/search

Price: 10 credits

Search IPO applications reviewed by the Shanghai Stock Exchange for the main board and the STAR Market, by issuer or intermediary name, board and review stage: issuer, status, planned raise, industry, province, application and update times, issuer executives and the sponsor, accounting firm, law firm and appraiser with their signing staff

How to use it

`keyword` matches intermediaries too, so a broker name returns the projects it sponsors. Pass `id` to sse/ipo-projects for the review timeline 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: 1300)
• keyword string nullable — Issuer or intermediary name to match (examples: "中信证券", "科技"; minLength: 1)
• board string nullable — Board applied for; both when omitted (one of: "main", "star")
• status string nullable — Current review stage (one of: "accepted", "inquiry", "listing_committee", "registration_submitted", "registration_result", "issued", "suspended", "terminated", "review_committee", "supplementary_review")
• sort string — Result order (default: "updated_newest"; one of: "updated_newest", "updated_oldest", "applied_newest", "applied_oldest")

Response

• @type string (default: "SseIpoProject")
• id string required
• url string required
• company_name string nullable
• company_short_name string nullable
• company_stock_code string nullable
• uniform_credit_code string nullable
• board string nullable
• status string nullable
• status_code integer nullable
• committee_result_code integer nullable
• registration_result_code integer nullable
• suspension_code integer nullable
• project_type_code integer nullable
• planned_raise_cny number nullable
• industry_code string nullable
• industry string nullable
• province string nullable
• district string nullable
• applied_at integer nullable
• created_at integer nullable
• updated_at integer nullable
• issuer_people array (default: [])
  • @type string (default: "SseIpoPerson")
  • name string nullable
  • job_title string nullable
  • job_type_code integer nullable
  • person_id string nullable
• intermediaries array (default: [])
  • @type string (default: "SseIpoIntermediary")
  • name string nullable
  • short_name string nullable
  • role string nullable
  • intermediary_id string nullable
  • order integer nullable
  • people array (default: [])
    • @type string (default: "SseIpoPerson")
    • name string nullable
    • job_title string nullable
    • job_type_code integer nullable
    • person_id string nullable

Errors

• 422 — An unknown board, status or sort 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.