/twse/stocks/quotes

POST /api/twse/stocks/quotes

Price: 1 credit

Daily trading history of one Taiwan Stock Exchange security: open, high, low, close, change, volume in shares, trade value and number of transactions per trading day

How to use it

Newest day first; history starts at 2010-01-04. Without date_from the walk stops after 12 months with no trading, so pass date_from for a security that stopped trading earlier.

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 trading days to return (min: 1; max: 2000)
• company string required — Security code (examples: "2330", "0050")
• date_from integer nullable — Earliest trading day, as unix seconds; day-granular (examples: 1735689600)
• date_to integer nullable — Latest trading day, as unix seconds; day-granular (examples: 1790812800)

Response

• @type string (default: "TwseStockQuote")
• security_code string required
• date integer required
• volume_shares integer nullable
• trade_value integer nullable
• transactions integer nullable
• open number nullable
• high number nullable
• low number nullable
• close number nullable
• change number nullable
• is_change_comparable boolean nullable
• note string nullable

Errors

• 422 — company is not a 4-6 character security code, or date_to is before date_from 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.