/sinafinance/quotes/list

POST /api/sinafinance/quotes/list

Price: 5 credits

List the stocks of a Sina Finance market-centre list (all A-shares, an exchange or board, a Sina or Shenwan industry, a concept or a region) ranked by change, price, volume, amount, market capital, turnover, P/E or P/B, with each stock's quote

How to use it

hs_a lists every Shanghai and Shenzhen A-share; sh_a, cyb and kcb list Shanghai, ChiNext and STAR stocks, and new_blhy is an industry list.

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 stocks to return (min: 1; max: 6000)
• node string required — Sina market-centre list code (examples: "hs_a", "sh_a", "cyb", "kcb", "new_blhy")
• sort_by string — Ranking field (default: "change_percent"; one of: "change_percent", "price", "volume", "amount", "market_capital", "turnover_rate", "pe", "pb", "symbol")
• order string — Ranking direction (default: "desc"; one of: "desc", "asc")

Response

• @type string (default: "SinafinanceListedStock")
• symbol string required
• code string nullable
• name string nullable
• price number nullable
• change number nullable
• change_percent number nullable
• previous_close number nullable
• open number nullable
• high number nullable
• low number nullable
• bid number nullable
• ask number nullable
• volume number nullable
• amount number nullable
• turnover_rate number nullable
• pe number nullable
• pb number nullable
• market_capital number nullable
• float_market_capital number nullable
• tick_time string 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 — No Sina market-centre list 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.