/sse/market/block-trades

POST /api/sse/market/block-trades

Price: 5 credits

List block trades on the Shanghai Stock Exchange, for one company or the whole market: trade day, price, volume, amount and the buying and selling brokerage branches

How to use it

Newest first. Without a trade window the whole history is returned, back to 2005.

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 block trades to return (min: 1; max: 10000)
• company string nullable — Six-digit stock code; the whole market when omitted (examples: "600519"; minLength: 1)
• traded_from integer nullable — Earliest trade day, as unix seconds; day-granular (examples: 1767225600)
• traded_to integer nullable — Latest trade day, as unix seconds; day-granular (examples: 1790812800)

Response

• @type string (default: "SseBlockTrade")
• company_code string required
• company_name string nullable
• trade_date integer nullable
• price_cny number nullable
• volume_shares number nullable
• amount_cny number nullable
• buyer_branch string nullable
• seller_branch string nullable
• is_special_session boolean nullable

Errors

• 422 — company is not a six-digit stock code, or traded_to is before traded_from 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.