/szse/companies/price-history

POST /api/szse/companies/price-history

Price: 1 credit

Get the daily, weekly or monthly price candles of a security traded on the Shenzhen Stock Exchange: open, close, high, low, change, volume and amount for each period

How to use it

Newest period first; at most the latest 201 periods per interval. Volumes are in shares.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Six-digit stock code or SZSE stock page URL (examples: "000001", "300750", "https://www.szse.cn/certificate/individual/index.html?code=300750"; minLength: 1)
• interval string — Length of each candle (default: "day"; one of: "day", "week", "month")

Response

• @type string (default: "SzseCandle")
• company_code string required
• interval string required
• date integer required
• open_cny number nullable
• close_cny number nullable
• low_cny number nullable
• high_cny number nullable
• change_cny number nullable
• change_percent number nullable
• volume_shares integer nullable
• amount_cny number nullable

Errors

• 422 — company is not a six-digit stock code or SZSE stock 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 — No Shenzhen-traded security under that code 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.