Building an AI agent? Start with /llms.txt for the full site index.
Macroeconomics
Official monthly Taiwan government statistic (), one row per (item, month). Fields honestly mapped from the source CSV; unit= (USD mn). Machine-carried attribution (OGDL v1 ⇄ CC BY 4.0). Not a forecast, not a recommendation.
GET /v2/datasets/export-orders-monthlyThis dataset is in build and not yet queryable via the API. The coverage and honest limitations below are the real database state; it moves off "Building" once serving lands (targeted 8/1).
| Field | Type | Description |
|---|---|---|
stat_item | text | |
item_code | code | |
item_name | text | label |
value | numeric | (USD mn) |
unit | text | |
attribution | text | (first-class) |
4,590 rows, 1984-01..2026-06, 9. HONEST GAP: only 9 of the 12 official classes have an opendata CSV; 3 (//) have NO machine-readable file and are absent. OGDL v1 (OK, attribution required). ROC dates converted +1911; period_month = first-of-month.
A real response from this endpoint. Rows are returned under "data", and provenance is carried in the shape shown below — it is not identical across datasets, so read this page's rather than assuming another's.
{ "dataset_id": "export-orders-monthly", "row_count": 3, "data": [ { "dataset_key": "export_orders_monthly", "period_month": "2026-06-01", "stat_item": "<Chinese value - see the zh page>", "item_code": "<Chinese value - see the zh page>", "item_name": "<Chinese value - see the zh page>", "value": 40501.0, "unit": "<Chinese value - see the zh page>", "attribution": "<Chinese value - see the zh page>" }, { "dataset_key": "export_orders_monthly", "period_month": "2026-05-01", "stat_item": "<Chinese value - see the zh page>", "item_code": "<Chinese value - see the zh page>", "item_name": "<Chinese value - see the zh page>", "value": 37242.0, "unit": "<Chinese value - see the zh page>", "attribution": "<Chinese value - see the zh page>" }, { "dataset_key": "export_orders_monthly", "period_month": "2026-04-01", "stat_item": "<Chinese value - see the zh page>", "item_code": "<Chinese value - see the zh page>", "item_name": "<Chinese value - see the zh page>", "value": 35939.0, "unit": "<Chinese value - see the zh page>", "attribution": "<Chinese value - see the zh page>" } ]}Captured from the live API on 2026-07-20.
Chinese data values are shown as a marker here so this page stays in English; the /zh page shows them verbatim.
curl "https://api.twmarketdata.com/v2/datasets/export-orders-monthly?symbol=2330" \ -H "X-API-Key: sk_live_..."| Parameter | Required | Type | Description |
|---|---|---|---|
symbol | Yes | string | Ticker, e.g. 2330. |
start_date | No | string (YYYY-MM-DD) | Start of the query range. |
end_date | No | string (YYYY-MM-DD) | End of the query range. |
limit | No | integer | Maximum rows to return. |
A first call:
import requests resp = requests.get( "https://api.twmarketdata.com/v2/datasets/export-orders-monthly", params={"symbol": "2330"}, headers={"X-API-Key": "sk_live_..."},)resp.raise_for_status()print(resp.json()["data"])With a date-range filter:
import requests # The full verified example — the same call with every supported filter set.resp = requests.get( "https://api.twmarketdata.com/v2/datasets/export-orders-monthly", params={"symbol": "2330"}, headers={"X-API-Key": "sk_live_..."},)resp.raise_for_status()for row in resp.json()["data"]: print(row)This endpoint is GET /v2/datasets/export-orders-monthly. The full machine-readable schema (parameters, security, response envelope) lives in the OpenAPI spec.