/xueqiu/quotes/klines

POST /api/xueqiu/quotes/klines

Price: 20 credits

Get price history bars for a Shanghai, Shenzhen, Beijing, Hong Kong or US security from Xueqiu, from one minute to one year per bar: open, high, low, close, volume, turnover, valuation ratios, market capital, margin balance and Stock Connect holdings

How to use it

Bars come newest first, ending at end_at. Intraday periods reach back only over recent sessions.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• symbol string required — Xueqiu security symbol or quote page URL (examples: "SH600519", "00700", "AAPL", "https://xueqiu.com/S/SZ000001")
• count integer required — Max number of bars to return, newest first (min: 1; max: 5000)
• period string — Bar length (default: "day"; one of: "1m", "5m", "15m", "30m", "60m", "day", "week", "month", "quarter", "year")
• adjustment string — Price adjustment for splits and dividends (default: "forward"; one of: "forward", "backward", "none")
• end_at integer nullable — Latest bar time to include, as unix seconds; defaults to now (examples: 1767225600)

Response

• @type string (default: "XueqiuKline")
• symbol string required
• period string required
• started_at integer required
• open number nullable
• high number nullable
• low number nullable
• close number nullable
• change number nullable
• change_percent number nullable
• volume number nullable
• amount number nullable
• turnover_rate number nullable
• after_hours_volume number nullable
• after_hours_amount number nullable
• pe number nullable
• pb number nullable
• ps number nullable
• pcf number nullable
• market_capital number nullable
• margin_balance number nullable
• northbound_shares_held number nullable
• northbound_holding_ratio number nullable
• northbound_net_shares number nullable
• southbound_shares_held number nullable
• southbound_holding_ratio number nullable
• southbound_net_shares number nullable

Errors

• 422 — The request body did not validate 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 — Xueqiu has no security under that symbol 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.