/twse/market/daily-quotes

POST /api/twse/market/daily-quotes

Price: 10 credits

Closing quotes of every security on the Taiwan Stock Exchange for one trading day, warrants excluded: code and name, open, high, low, close, change, volume, value, transactions, last best bid and ask, and P/E ratio

How to use it

Rows are in security-code order; names are in Chinese. A day without trading returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• date integer nullable — Trading day, as unix seconds; the latest trading day when omitted (examples: 1790812800)
• count integer required — Max number of securities to return (min: 1; max: 2000)

Response

• @type string (default: "TwseDailyQuote")
• security_code string required
• date integer required
• security_name string nullable
• volume_shares integer nullable
• transactions integer nullable
• trade_value_twd integer nullable
• open number nullable
• high number nullable
• low number nullable
• close number nullable
• change number nullable
• best_bid_price number nullable
• best_bid_lots integer nullable
• best_ask_price number nullable
• best_ask_lots integer nullable
• pe_ratio number nullable

Errors

• 422 — count is out of range 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.

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.