🇹🇼 Taiwan Trade Statistics — UN Comtrade Exports & Imports

Pricing

Rating

Developer

Actor stats

Categories

Share

Real bilateral trade values for Taiwan — annual exports, imports and trade balance by partner country × HS commodity code — sourced live from the UN Comtrade public API.

⚠️ Important — what this data actually is (please read)

Taiwan (the Republic of China) is not a UN member, so the United Nations Statistics Division publishes Taiwan's merchandise-trade figures under the reporter label "Other Asia, nes" (reporter code 490) — a residual area that is predominantly Taiwan. This actor returns those real UN Comtrade values.

• ✅ The values are real, fetched live from UN Comtrade — nothing is estimated, simulated, or generated by this actor.
• ⚠️ They are labelled "Other Asia, nes (≈ Taiwan)" in every row (reporter_label + data_source). They are not exact figures from Taiwan's own Customs Administration / Bureau of Foreign Trade.
• ⚠️ Data is annual (calendar year). UN Comtrade does not publish monthly data for this reporter.
• ⚠️ Values are in USD only (FOB for exports, CIF for imports). UN Comtrade does not publish TWD for this reporter, so no NT$ figure is included.
• ⚠️ Annual data lags ~1–2 years and coverage varies by cell. If a year/partner/HS combination has no published data, the actor emits a single non-billed status row explaining this.

If you specifically need exact official ROC customs figures by month, those live in Taiwan's own customs systems (web.customs.gov.tw / cus93.trade.gov.tw), which are not openly queryable from automated infrastructure; this actor uses UN Comtrade as the reachable, real, internationally-standardised alternative.

📊 Sample Output

👁 Taiwan trade statistics — annual partner-country × HS commodity exports / imports / trade balance in USD, from UN Comtrade reporter Other Asia nes (≈ Taiwan), for semiconductor (HS 85, 8542, 8471) supply-chain analysts and EM macro research

⚡ What you get

All fields are nullable — real data has gaps and this schema reflects that.

trade_balance rows are computed as (real export value − real import value) for the same year/partner/HS cell; both inputs are fetched live, so the balance is derived from real figures, not invented.

🎯 Use cases

1. Semiconductor-cycle macro read. HS 8542 (integrated circuits) and 8471 (computers) exports to China / Hong Kong / USA are the clearest read on the TSMC–MediaTek–UMC cycle. Comtrade's "Other Asia, nes" series captures the bulk of this.
2. APAC supply-chain mapping. Track Taiwan–Vietnam / Taiwan–Malaysia trade (HS 85, 84) to monitor fab + assembly relocation out of Mainland China.
3. EM macro research. Annual electronics-export and trade-balance levels by partner for structural TWD and current-account analysis.
4. Trade-policy research. Compare Taiwan's trade by HS chapter and partner across years for tariff / supply-chain studies.
5. AI agent / data integration. Wire real, source-traceable Taiwan trade values into an LLM research agent or dashboard.

🚀 How to use

Sample (exports to US, integrated circuits):

{
"data_type":"exports",
"partner_country_filter":"US",
"hs_code_filter":"8542",
"date_from":"2022-01-01",
"date_to":"2022-12-31",
"max_records":5
}

Trade balance vs Mainland China, electronics:

{
"data_type":"trade_balance",
"partner_country_filter":"CN",
"hs_code_filter":"85",
"date_from":"2021-01-01",
"date_to":"2023-12-31",
"max_records":20
}

Default sweep (top partners × top HS classes, recent years):

{
"data_type":"all",
"max_records":100
}

partner_country_filter accepts an ISO-3166-1 alpha-2 code (US, CN, JP, KR, HK, SG, DE, VN, MY, TH, …) or a raw UN M49 numeric code. date_from / date_to select the year range (the day/month are ignored — data is annual).

⚙️ How it works

For each (year, HS code, partner) in your query the actor issues a live request to the UN Comtrade public preview endpoint:

GEThttps://comtradeapi.un.org/public/v1/preview/C/A/HS
?reporterCode=490&period={year}&flowCode={X|M}&cmdCode={hs}&partnerCode={m49}

and emits the returned primaryValue verbatim. Partner names come from UN Comtrade's own partnerAreas.json reference table. The endpoint is keyless but rate-limited, so the actor paces requests; very large sweeps may take a few minutes.

💲 Pricing

This actor uses Apify pay-per-event pricing:

You are charged only for real trade records returned. Probe, error, empty and status rows are not charged.

Start free on Apify →

❓ FAQ

Is this official Taiwan customs data? No — it is UN Comtrade's "Other Asia, nes" (reporter 490) series, which is predominantly Taiwan and is the internationally-standardised proxy. Every row says so explicitly via reporter_label and data_source.

Why annual and not monthly? UN Comtrade does not publish monthly data for reporter 490. Only annual data is available, so period is a year.

Why USD only, no NT$? UN Comtrade reports this series in current USD; it does not publish TWD for this reporter. No TWD value is fabricated.

Why did a run return a status row? That year/partner/HS combination has no published Comtrade data (often because annual data lags 1–2 years, or that specific cell isn't reported). Try an earlier year, a broader HS code (e.g. TOTAL), or a different partner. status rows are not billed.

How current is the data? Annual data lags ~1–2 years. By default the actor queries the three most recent prior calendar years.

📚 Source & legal

Data: UN Comtrade (United Nations Statistics Division), public API, reporter 490 "Other Asia, nes". Use is subject to UN Comtrade's terms and attribution requirements. This actor is an access/transformation tool; it does not modify the underlying values.

ℹ️ About

Built by NexGenData. Contact: hello@thenextgennexus.com