/sinafinance/quotes

POST /api/sinafinance/quotes

Price: 1 credit

Get real-time quotes from Sina Finance for Shanghai, Shenzhen and Beijing stocks with a five-level order book, Hong Kong and US stocks, mutual fund net values and index levels, many symbols in one call

How to use it

A six-digit code is read as a mainland stock, five digits as Hong Kong and letters as a US ticker; funds take f_ and indices s_ before the code, as in f_000001 and s_sh000001. Find symbols with sinafinance/quotes/search. A symbol Sina does not know is left out.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• symbols array required — Sina Finance quote symbols, stock codes or tickers (examples: ["sh600519","600519","00700","AAPL","f_000001","s_sh000001"]; minItems: 1; maxItems: 50)

Response

• @type string (default: "SinafinanceQuote")
• symbol string required
• kind string required
• name string nullable
• name_en string nullable
• price number nullable
• previous_close number nullable
• open number nullable
• high number nullable
• low number nullable
• change number nullable
• change_percent number nullable
• volume number nullable
• amount number nullable
• bid number nullable
• ask number nullable
• bids array (default: [])
  • @type string (default: "SinafinanceOrderLevel")
  • price number required
  • volume number nullable
• asks array (default: [])
  • @type string (default: "SinafinanceOrderLevel")
  • price number required
  • volume number nullable
• high_52w number nullable
• low_52w number nullable
• eps number nullable
• pe number nullable
• market_capital number nullable
• total_shares number nullable
• extended_price number nullable
• extended_change number nullable
• extended_change_percent number nullable
• nav number nullable
• accumulated_nav number nullable
• previous_nav number nullable
• nav_date integer nullable
• updated_at integer 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 — None of the symbols is known to Sina Finance 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.