POST /api/sse/companies/trading-stats
Price: 1 credit
Get the trading statistics of a Shanghai-listed stock for one day, month or year: open, close, high and low prices, change, swing, turnover rate, P/E, volume, amount, market capitalisation and the period's highest and lowest volume and amount days
A non-trading day, a period before listing or an unknown code returns an empty list. Volumes are in shares, money in CNY.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)company string required — Six-digit A-share stock code or SSE company page URL (examples: "600519", "688981", "https://www.sse.com.cn/assortment/stock/list/info/company/index.shtml?COMPANY_CODE=600519"; minLength: 1)period string — Length of the statistics period (default: "day"; one of: "day", "month", "year")date integer nullable — A day inside the wanted period, as unix seconds; the latest period when omitted (examples: 1790640000)@type string (default: "SseTradingStats")company_code string requiredcompany_name string nullableperiod string nullabletrade_date integer nullableperiod_month string nullableperiod_year integer nullabletrading_days integer nullableopen_price_cny number nullableclose_price_cny number nullablehigh_price_cny number nullablehigh_price_date integer nullablelow_price_cny number nullablelow_price_date integer nullablechange_cny number nullablechange_percent number nullableswing_percent number nullableturnover_percent number nullablepe_ratio number nullablevolume_shares number nullableamount_cny number nullablemarket_cap_cny number nullablefloat_market_cap_cny number nullablehigh_volume_shares number nullablehigh_volume_date integer nullablelow_volume_shares number nullablelow_volume_date integer nullablehigh_amount_cny number nullablehigh_amount_date integer nullablelow_amount_cny number nullablelow_amount_date integer nullable422 — company is not a six-digit stock code or SSE company page URL 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.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.