Open Company Data in Taiwan: Official Sources, APIs and Reuse Rights

Taiwan is one of the clearest open-company-data opportunities in Asia because its official ecosystem combines data.gov.tw company-registration API datasets, the GCIS open-data platform, Swagger/OpenAPI documentation, an official Open Government Data License, Ministry of Finance business tax registration data, procurement notice datasets, listed-company disclosures, IP sources, financial regulator context and GLEIF legal-entity identifiers. That does not make every business use automatic. The correct editorial view is to separate company registration, business registration, tax registration, procurement participation, listed-company disclosure, IP ownership, LEI coverage and contact-data use.

This refresh is written for analysts, KYB teams, data buyers and market-research users who need a practical source map rather than a thin list of links. It explains which Taiwan sources are official, which are API or bulk-friendly, which are enrichment-only, and which claims remain blocked under attribution, privacy, source terms and marketing-contact rules.

The live CompaniesData Taiwan article was already public at https://companiesdata.cloud/open-company-data-taiwan.html, but the current editorial standard now requires a deeper reference article. The source recheck on 2026-06-09 found 13 publication-safe official/high-quality sources, 1 held route and no hard 404/410 failures. The held route in this node is: Taiwan e-Procurement portal.

Key Takeaways

• Best core source: data.gov.tw company-registration API datasets and GCIS documentation are the strongest official evidence for Taiwan company data.
• Best reuse frame: Taiwan’s Open Government Data License v1.0 supports broad reuse where a dataset uses it, but attribution, no-misrepresentation and dataset-specific terms still matter.
• Best enrichment stack: Ministry of Finance tax registration, procurement notice data, MOPS/TWSE, TIPO, FSC and GLEIF add useful layers around the registry core.
• Best caution: company, business and tax registration data are not sales-prospecting permission and should not be sold as email or phone consent.
• CompaniesData value: Taiwan is source-rich, but production users still need normalization, source provenance, update tracking, field matching and lawful-use separation.

Editorial Methodology

The CompaniesData country method starts with official sources, then classifies each source by authority, access model, reuse note, business use and limitation. Registry API datasets, licence pages, tax datasets, procurement data, exchange filings, IP offices, financial regulators and LEI records are not interchangeable because each proves a different claim.

For this Taiwan refresh, only sources that returned stable content or API data in the recheck are linked as clean evidence. The Taiwan e-Procurement portal remains a held source because it timed out from this node, even though procurement notice data on data.gov.tw passed as a clean official alternative. This avoids linking an unstable portal route as if it were verified crawlable evidence.

Source logos and favicons are used as decorative recognition cues in the source matrix and Resource Pack. They do not replace the evidence: official URL, public owner, access model, reuse note and source limitation remain the proof.

Coverage, Access and Update-Risk Analysis

Company-registration API backbone: data.gov.tw and GCIS provide the most important official route for Taiwan company registration information. The key editorial claim is API-positive and official, not that every filing or beneficial-owner detail is present in one free file.

Business vs company registration: Taiwan source names can mix company registration, business registration and tax registration concepts. A normalized dataset should preserve the source category for each field instead of collapsing every identifier into one generic company table.

Licence scope: Open Government Data License v1.0 is strong evidence for reuse where it applies, but users still need attribution, no-misrepresentation handling, source-owner acknowledgement and privacy review. A licence page is not a shortcut around personal-data or sector-specific constraints.

Tax-registration layer: the Ministry of Finance business tax registration dataset is valuable for status and business-tax context, but it is an enrichment layer. It should be reconciled to company-registration records using stable identifiers and update timestamps.

Procurement scope: data.gov.tw procurement notice data supports tender and agency pipeline analysis. It does not prove every supplier, contract, beneficial owner or current legal status.

Listed-company and regulator scope: MOPS/TWSE and FSC sources are strong for regulated and listed subsets. They should carry subset flags because they do not cover the full Taiwan business universe.

IP and LEI scope: TIPO and GLEIF improve matching confidence where entities hold IP rights or LEIs. Coverage is partial and should be joined as enrichment, not projected onto every company.

Reuse Checklist

• Authority check: store whether a field came from data.gov.tw, GCIS, MOEA, Ministry of Finance, PCC, MOPS/TWSE, TIPO, FSC or GLEIF.
• Licence check: preserve whether the dataset explicitly uses Open Government Data License v1.0 or another source-specific term.
• Attribution check: keep source owner, dataset title, URL, access date and licence reference available in customer documentation.
• No-misrepresentation check: avoid wording that implies government endorsement of CompaniesData or a derived product.
• Field check: separate company registration, business registration, tax registration, procurement events, listed-company disclosures, IP records and LEIs.
• Privacy check: flag natural-person-adjacent, representative, address and contact-like fields before reuse.
• Marketing check: keep official company identity and contact-data enrichment as separate workflows with separate lawful basis review.
• Coverage check: mark whether a record is a registered company, tax-registered business, procurement notice participant, listed company, IP owner or LEI holder.
• Update check: capture source update frequency, data snapshot date, local ingestion date, parser version and transform version.

Resource Pack

Source-by-Source Deep Dives

1. Basic Company Registration Information – Application Two

Authority: Administration of Commerce, Ministry of Economic Affairs. Type: official company registration API dataset. Access model: JSON/XML API via data.gov.tw and GCIS OAS documentation. Reuse note: Open Government Data License v1.0.

Company registration lookup using unified business number and official API metadata. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: API route, not a full corporate filing archive or marketing-contact permission. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

2. Basic Company Registration Information – Application One

Authority: Administration of Commerce, Ministry of Economic Affairs. Type: official company registration open dataset. Access model: API / structured data. Reuse note: Open Government Data License v1.0.

Company registration fields and data dictionary context. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: Chinese-first dataset page and endpoint-specific field coverage. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

3. GCIS open data platform

Authority: Administration of Commerce / MOEA. Type: official commerce open-data platform. Access model: API / datasets / documentation. Reuse note: Open-data and dataset-specific terms.

Official registry open-data discovery for company and business registration datasets. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: Dataset-level terms and field coverage must be checked before reuse. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

4. GCIS Swagger API docs

Authority: Administration of Commerce / MOEA. Type: official API documentation. Access model: Swagger / OpenAPI documentation. Reuse note: Open-data API terms.

Programmatic endpoint evidence for company and business registration services. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: Swagger docs prove endpoints, not legal completeness of every field. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

5. Company registration public data digital application

Authority: Administration of Commerce / MOEA. Type: official company public-data application route. Access model: application workflow / downloadable delivery. Reuse note: MOEA application and reuse terms.

Evidence that company registration public data may also be requested in digital format. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: Application workflow; not the same as an unrestricted anonymous bulk endpoint. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

6. Company registration enquiry

Authority: MOEA company registration service. Type: official company registration enquiry. Access model: search / enquiry workflow. Reuse note: MOEA website and service terms.

Manual live-company and registration-case inquiry route. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: Search workflow, not a bulk download; may be session or form dependent. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

7. Taiwan Open Government Data License

Authority: Ministry of Digital Affairs / data.gov.tw. Type: official open-data license. Access model: license page. Reuse note: Open Government Data License v1.0.

Reuse, attribution and no-misrepresentation frame for data.gov.tw datasets. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: License applies where the dataset explicitly uses it; privacy and source-specific constraints still matter. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

8. National Business Tax Registration Information Dataset

Authority: Fiscal Information Agency, Ministry of Finance. Type: official business tax registration dataset. Access model: dataset page / CSV / OAS API documentation. Reuse note: Open Government Data License v1.0.

Tax-registration enrichment and daily-updated business status context. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: Tax registration scope; must be normalized against company registration and not treated as lead-list permission. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

9. Procurement notice dataset

Authority: Public Construction Commission, Executive Yuan. Type: official procurement open data. Access model: XML / daily open dataset. Reuse note: Open Government Data License v1.0.

Tender pipeline and agency procurement enrichment. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: Procurement notice layer only; not all suppliers or registered companies. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

10. MOPS/TWSE

Authority: Taiwan Stock Exchange / regulator disclosure. Type: listed-company disclosure system. Access model: filings / search. Reuse note: MOPS/TWSE terms.

Listed-company filings and regulated-market enrichment. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: Listed-company scope only. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

11. Taiwan Intellectual Property Office

Authority: official IP. Type: official IP office. Access model: search / services / publications. Reuse note: TIPO terms.

Trademark, patent and IP enrichment. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: IP layer only, not company-register coverage. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

12. Financial Supervisory Commission

Authority: official financial regulator. Type: financial regulator. Access model: registers / publications / supervision. Reuse note: FSC website and publication terms.

Financial-sector regulated-entity context. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: Sector-specific, not general company-register coverage. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

13. GLEIF LEI records for Taiwan

Authority: global official LEI system. Type: LEI API. Access model: public API. Reuse note: GLEIF open data licence with attribution and no-endorsement conditions.

Cross-border legal-entity identifier enrichment for Taiwanese entities with LEIs. For CompaniesData ingestion, keep URL, access date, source owner, licence note and field provenance before joining this source to another Taiwan entity layer.

Limitation: LEI coverage is partial and skewed toward financial/cross-border entities. This is one evidence layer, not proof of complete coverage, official endorsement, beneficial-ownership completeness or contact-data permission.

Practical Manual, API and Bulk Options

1. data.gov.tw company-registration API route

Start with the data.gov.tw company-registration API datasets and follow the documented GCIS OAS/Swagger routes. Store the exact dataset id, endpoint documentation URL, update frequency, licence and source-owner details before building any downstream table.

2. GCIS platform route

Use the GCIS open-data platform and Swagger documentation as the technical source of truth for endpoint structure. Keep endpoint versions and field mappings in version control because API documentation can change independently from public article text.

3. Digital application route

The official public-data application page is useful evidence that company registration data can also be requested in digital form. Treat it as an application workflow, not as proof of anonymous unrestricted bulk access.

4. Tax-registration dataset route

Use the Ministry of Finance business tax registration dataset for daily-updated business-tax context. Join it with company-registration data using stable identifiers and keep tax-registration status separate from legal-company status.

5. Procurement, listed-company, IP and LEI route

Use procurement notice data, MOPS/TWSE, TIPO, FSC and GLEIF as enrichment layers. Each source adds a useful business signal, but each one has partial coverage and should carry a subset flag in the CompaniesData model.

Held Source-Risk Findings

• Taiwan e-Procurement portal: source-relevant but timed out from this node. Do not link the portal as clean evidence until browser or route QA clears it.
• Procurement alternative: the data.gov.tw procurement notice dataset passed QA and can support procurement discussion without relying on the unstable portal homepage.
• Session-dependent enquiry: any form or session route should be described as manual/search access, not bulk API proof.
• Complete filing claim: blocked. The clean sources support strong API and open-data claims, but not every filing, corporate act or beneficial-owner detail in one file.
• Marketing-contact claim: blocked. Public registry, tax, procurement or listed-company data is not sales-prospecting permission.

Missing-Data Gaps

• Beneficial ownership: do not claim complete public beneficial-ownership coverage from the clean source set.
• Corporate acts: registration APIs and enquiry routes do not necessarily expose every historical act or document image.
• Real-time status: datasets with hourly or daily updates still need source timestamps and local ingestion timestamps.
• Contact fields: business emails, phones and outreach contacts are a separate compliant enrichment layer.
• Language normalization: Chinese-first source data requires careful transliteration, alias and English-name handling.
• Subset data: procurement notices, MOPS/TWSE, TIPO, FSC and LEI records cover subsets that must not be treated as universal.

Recommended Data Model

• Entity table: CompaniesData id, unified business number, legal name, registration type, status, source owner, source date and normalization version.
• Business registration table: business-registration fields, tax-registration status, source id, dataset date and reconciliation confidence.
• Name and alias table: Chinese name, English name where present, transliteration, normalized token form, matching confidence and source provenance.
• Address table: registered address, parsed administrative area, postal code where present, geocoding confidence and privacy flags.
• Procurement table: procurement notice id, agency, tender case number, tender name, scheduled date and supplier/participant fields when present.
• Listed-company table: MOPS/TWSE identifiers, issuer name, market category, disclosure URL and listed-company subset flag.
• IP table: TIPO trademark or patent identifiers, owner string, class/category, status and matching confidence.
• LEI table: LEI, legal name, registration status, managing LOU, GLEIF update timestamp and Taiwan subset flag.
• Compliance flags: open-data-attribution, no-endorsement, privacy-review, contact-use-blocked, procurement-only, listed-subset, lei-subset and manual-review-required.

CompaniesData Normalization and Enrichment Value

Taiwan is a strong official-source market, but raw API access is not the same as a production-ready international dataset. CompaniesData turns official material into a usable business dataset by normalizing identifiers, preserving source provenance, separating company, business and tax registration layers, matching listed-company and IP records, adding update tracking and documenting lawful-use boundaries.

For international users, the strategic route is CompaniesData.cloud because the dataset can be packaged with English documentation, stable columns, source notes and lawful-use cautions. Request a CompaniesData sample for Taiwan if you need a normalized dataset rather than a list of source portals. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the owned route; however, that contact-data layer remains separate from official open-data reuse.

Important boundary: CompaniesData can enrich Taiwan company records for analysis, KYB, CRM cleanup, market research and sourcing workflows. That is not the same as saying public official records are automatically valid for cold email, phone lists, messaging campaigns or unrestricted resale.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Basic Company Registration Information – Application Two	Administration of Commerce, Ministry of Economic Affairs	JSON/XML API via data.gov.tw and GCIS OAS documentation	Open Government Data License v1.0	API route, not a full corporate filing archive or marketing-contact permission.
Basic Company Registration Information – Application One	Administration of Commerce, Ministry of Economic Affairs	API / structured data	Open Government Data License v1.0	Chinese-first dataset page and endpoint-specific field coverage.
GCIS open data platform	Administration of Commerce / MOEA	API / datasets / documentation	Open-data and dataset-specific terms	Dataset-level terms and field coverage must be checked before reuse.
GCIS Swagger API docs	Administration of Commerce / MOEA	Swagger / OpenAPI documentation	Open-data API terms	Swagger docs prove endpoints, not legal completeness of every field.
Company registration public data digital application	Administration of Commerce / MOEA	application workflow / downloadable delivery	MOEA application and reuse terms	Application workflow; not the same as an unrestricted anonymous bulk endpoint.
Company registration enquiry	MOEA company registration service	search / enquiry workflow	MOEA website and service terms	Search workflow, not a bulk download; may be session or form dependent.
Taiwan Open Government Data License	Ministry of Digital Affairs / data.gov.tw	license page	Open Government Data License v1.0	License applies where the dataset explicitly uses it; privacy and source-specific constraints still matter.
National Business Tax Registration Information Dataset	Fiscal Information Agency, Ministry of Finance	dataset page / CSV / OAS API documentation	Open Government Data License v1.0	Tax registration scope; must be normalized against company registration and not treated as lead-list permission.
Procurement notice dataset	Public Construction Commission, Executive Yuan	XML / daily open dataset	Open Government Data License v1.0	Procurement notice layer only; not all suppliers or registered companies.
MOPS/TWSE	Taiwan Stock Exchange / regulator disclosure	filings / search	MOPS/TWSE terms	Listed-company scope only.
Taiwan Intellectual Property Office	official IP	search / services / publications	TIPO terms	IP layer only, not company-register coverage.
Financial Supervisory Commission	official financial regulator	registers / publications / supervision	FSC website and publication terms	Sector-specific, not general company-register coverage.
GLEIF LEI records for Taiwan	global official LEI system	public API	GLEIF open data licence with attribution and no-endorsement conditions	LEI coverage is partial and skewed toward financial/cross-border entities.

FAQ

Is Taiwan a strong open company data country?

Yes. Taiwan is one of the strongest Asia candidates because official company-registration API datasets, GCIS documentation and the Open Government Data License create a clear open-data foundation.

What is the best first source for Taiwan company data?

Start with data.gov.tw company-registration API datasets and GCIS Swagger/OpenAPI documentation, then use MOEA enquiry routes for manual checks where appropriate.

Does Taiwan have a reusable open-data licence?

Yes, many official datasets use Open Government Data License v1.0. Users still need attribution, no-misrepresentation handling, privacy review and dataset-specific source checks.

Is the Ministry of Finance tax dataset a company register?

No. It is an official business tax registration dataset and a useful enrichment layer, but it should be normalized against company-registration data rather than treated as the same source.

Can procurement data identify all Taiwan companies?

No. Procurement notice data supports tender and public-procurement context, but it only covers procurement activity and related public-sector events.

Why hold the Taiwan e-Procurement portal?

The portal timed out from this QA node. It can be rechecked manually or replaced with stable official data.gov.tw procurement datasets for public evidence.

Can open Taiwan registry data be used for cold outreach?

No. Public company, business or tax registration data is not sales-prospecting permission. Contact-data enrichment needs separate lawful basis, suppression and opt-out controls.

Why use CompaniesData if Taiwan has official APIs?

Because raw APIs still need entity resolution, bilingual normalization, provenance, update tracking, enrichment joins, privacy flags and delivery in formats that business teams can actually use.

Official Sources

• Basic Company Registration Information – Application Two – Administration of Commerce, Ministry of Economic Affairs
• Basic Company Registration Information – Application One – Administration of Commerce, Ministry of Economic Affairs
• GCIS open data platform – Administration of Commerce / MOEA
• GCIS Swagger API docs – Administration of Commerce / MOEA
• Company registration public data digital application – Administration of Commerce / MOEA
• Company registration enquiry – MOEA company registration service
• Taiwan Open Government Data License – Ministry of Digital Affairs / data.gov.tw
• National Business Tax Registration Information Dataset – Fiscal Information Agency, Ministry of Finance
• Procurement notice dataset – Public Construction Commission, Executive Yuan
• MOPS/TWSE – Taiwan Stock Exchange / regulator disclosure
• Taiwan Intellectual Property Office – official IP
• Financial Supervisory Commission – official financial regulator
• GLEIF LEI records for Taiwan – global official LEI system