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

Thailand should now be treated as a strong official-source market for company-data research, but not as a simple unrestricted bulk-download market. The key update is that the DBD-owned Open-DBD portal and its juristic-person dataset pages cleared strict browser, Googlebot and Bingbot source-live checks on 2026-06-14. That changes the practical editorial route: the article no longer needs to lean on the blocked DBD DataWarehouse interface as the main evidence for reusable company data.

The safe source stack starts with the Department of Business Development (DBD), Open-DBD active juristic-person datasets, DBD certificate verification and DBD service context. It then adds regulator, financial-sector and identifier enrichment from SEC iDISC, the Bank of Thailand and GLEIF. DataWarehouse, general data.go.th, tax/VAT search, procurement, IP search and market-data routes are still useful in manual research, but they should not be presented as clean open bulk company data unless a final publication check clears the exact route and terms.

This article is a practical reference for Thailand company-data work. It separates clean official dataset evidence from controlled lookup routes, records the source limits that matter for reuse, and explains where CompaniesData normalization adds value after the official source layer.

Key takeaways

Core official source: DBD remains the registry authority for Thai juristic-person data, registration services and company-document workflows.
Material new evidence: Open-DBD provides DBD-owned dataset pages for active juristic-person data and juristic-person counts, and those pages passed strict live-source checks in this cycle.
Controlled lookup caveat: DBD DataWarehouse is still an official lookup route, but it returned Incapsula/redirect blockers and must stay out of clean-link claims until it clears final QA.
Reuse caution: Open-DBD raises API/bulk confidence to medium, but it does not automatically permit unrestricted all-field reuse, scraping, endorsement claims or contact-data marketing.
Enrichment layers: SEC iDISC, the Bank of Thailand, SET, Revenue Department, procurement, IP and GLEIF sources are useful overlays, not substitutes for DBD registry coverage.
CompaniesData value: Thailand needs normalization across Thai/English names, identifiers, activity fields, addresses, source provenance, update dates and lawful-use flags.

Editorial methodology

This Thailand refresh follows an official-source-first method. Each source is classified by owner, authority, access model, reuse terms, commercial-data role and live accessibility. Source-live QA distinguishes browser access from Googlebot and Bingbot access because a public article should not cite a source that only works for one profile or returns a bot-protection shell to crawlers.

The method also separates registry evidence from enrichment evidence. DBD and Open-DBD support the core identity layer. DBD certificate verification supports document validation. DBD Biz Regist and DBD service pages explain workflows, not reusable datasets. SEC, SET and Bank of Thailand sources cover listed or regulated entities. Revenue VAT search is a tax-identifier route with privacy and lawful-use limits. GLEIF is high-quality but partial because only Thai entities with LEIs appear there.

This article links only routes that are clean or intentionally conditional with clear caveats. Routes currently held from clean-link claims are: DBD DataWarehouse, Thailand Open Government Data, Thailand Open Government Data API documentation, DGA Open Government Data service, Thai e-GP, Thai SEC home, SET securities list, Department of Intellectual Property, DIP search, Revenue Department VAT search. Those can be mentioned as controlled or manual research routes, but they should not be used as evidence for open bulk access or automatic reuse.

This refresh adds methodology, source-by-source notes, access-risk analysis, a reuse checklist, recommended data model, resource pack, FAQ and explicit contact-data cautions so the page works as a deep reference rather than a thin source list.

Coverage, access and update-risk analysis

Thailand’s company-data ecosystem is relatively sophisticated. The DBD authority site and Open-DBD datasets create a defensible official foundation for juristic-person research. The clean Open-DBD routes are especially important because they move the article from a portal-listing page to a reference article grounded in dataset-level evidence.

Coverage still has limits. A DBD dataset may expose registered juristic-person facts, but the exact fields, update rhythm, resource endpoints and reuse notes must be preserved in downstream work. The registration dataset is not the same as a guarantee of every document, every historical event, every beneficial-owner field, every tax record or every contact channel. A serious data model should keep registry identity, documents, tax identifiers, procurement activity, listed-company disclosures and LEI identifiers in separate tables or source layers.

Access risk remains real. DBD DataWarehouse is source-relevant but blocked under current strict probes. General data.go.th and DGA routes were also noisy or blocked. Thai e-GP, IP and tax routes may return pages but still need semantic, source-term and privacy review before they become clean publication links. This matters because a public article that gives users a blocked link degrades trust, and a data product that treats controlled lookups as open bulk data creates legal and operational risk.

Update risk should be handled with source dates and field provenance. Open-DBD dataset pages may change resource links, field names, update timestamps, licence text or API behavior. DBD service pages may change URLs or require JavaScript. Regulator and market-data sites may revise terms. For CompaniesData-style processing, that means every record should carry source URL, source family, access date, update date where available, ingestion timestamp and a clear confidence score.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Limitation
Department of Business Development	Department of Business Development, Ministry of Commerce	official portal / services / registry authority	DBD website and service terms	Institutional portal, not proof of unrestricted public bulk company-register data.
Open-DBD portal	Department of Business Development, Ministry of Commerce	CKAN/OpenD public data catalogue	dataset-specific terms; Open Data Common appears on DBD dataset pages	Portal-level evidence; dataset page and resource terms still control reuse.
Open-DBD active juristic-person group	Department of Business Development, Ministry of Commerce	dataset group / public catalogue	dataset-specific terms; Open Data Common appears on dataset pages	Group page confirms dataset family but not all downstream field or API limits.
Open-DBD juristic-person registration dataset	Department of Business Development, Ministry of Commerce	public JSON dataset and download route	Open Data Common; no access restriction stated on dataset page	Dataset fields and API/download route need source-specific validation; not permission for contact-data marketing.
Open-DBD juristic-person count dataset	Department of Business Development, Ministry of Commerce	public JSON statistics dataset and download route	Open Data Common; no access restriction stated on dataset page	Aggregate/statistical dataset, not complete entity microdata by itself.
DBD English certificate verification	Department of Business Development	certificate-reference verification	DBD certificate-verification terms	Reference-based verification only; not company-register bulk access.
DBD Biz Regist	Department of Business Development	online registration / service portal	DBD service terms	Registration workflow, not a reusable open company dataset.
DBD DataWarehouse+ service page	Department of Business Development, Ministry of Commerce	service page / DataWarehouse context	DBD website and service terms	Service explainer only; not an open bulk/API dataset.
DBD business data services category	Department of Business Development, Ministry of Commerce	service category / business data services	DBD website and service terms	Service navigation only; source-specific dataset and service terms still apply.
DBD online services for juristic persons	Department of Business Development, Ministry of Commerce	online service gateway	DBD e-service terms	Service gateway, not reusable open company data.
Thai SEC iDISC listed company profiles	Securities and Exchange Commission Thailand	public disclosure search	SEC disclosure terms	Listed companies only; not a national company-register substitute.
Bank of Thailand financial institutions list	Bank of Thailand	official list / supervised financial institutions	Bank of Thailand website terms	Sector-specific list only.
GLEIF LEI records for Thailand	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.

Claims allowed and not allowed

Claims this source set supports

Official registry authority: Thailand has a central DBD authority that anchors juristic-person registration and business-service context.
Official dataset evidence: Open-DBD provides DBD-owned public dataset pages for active juristic-person data and juristic-person counts when final source-live QA remains clean.
Controlled lookup context: DBD DataWarehouse can be described as an official controlled lookup route, but not as a clean open bulk route in its current blocked state.
Regulated-entity enrichment: SEC iDISC and Bank of Thailand sources support listed-company or financial-sector overlays, not the entire company universe.
Identifier enrichment: GLEIF can add LEI identifiers for a partial, high-quality subset of Thai entities.
Normalization value: A commercial data product can add value through matching, provenance, deduplication, multilingual handling and lawful-use controls.

Claims this source set does not support

No unrestricted all-field claim: do not say every DBD field is freely reusable for any purpose without preserving dataset-specific terms and final source evidence.
No DataWarehouse scraping claim: blocked DataWarehouse access does not support claims that the lookup is safely crawlable or scrapeable.
No all-company coverage from subsets: procurement, listed-company, financial-institution, IP, VAT and LEI sources are partial overlays.
No beneficial-ownership completeness claim: this cycle did not verify a clean public BO dataset suitable for publication claims.
No marketing permission: public registry, VAT, officer, address, phone, email or procurement evidence is not permission to create lead lists.

Source-by-source deep dives

Department of Business Development

DBD is the editorial anchor. It identifies the Thai authority responsible for business development, registration services and official company-data context. The DBD authority site is useful for explaining who owns the system and where registry services fit. It is not, by itself, a bulk dataset. The article should use DBD as the institutional owner and then point to Open-DBD dataset pages for reusable evidence.

Open-DBD portal and juristic-person datasets

Open-DBD is the most important improvement in this cycle. The portal, active juristic-person group, juristic-person registration dataset and juristic-person count dataset passed browser, Googlebot and Bingbot checks. This gives the Thailand article a clean DBD-owned source path for official dataset discussion. The correct claim is that DBD provides public dataset pages that can support company-data analysis with source-specific terms, not that every downstream commercial use is automatically unrestricted.

For ingestion planning, Open-DBD should be treated as the primary dataset-discovery route. A data pipeline should capture dataset URL, resource URL, licence label, update date, field list and API/download behavior. Ongoing QA should verify the Open-DBD pages still return real content rather than a challenge page or JavaScript shell.

DBD DataWarehouse and DBD service pages

DBD DataWarehouse remains source-relevant because it is the familiar juristic-person and financial-statement lookup route. In this cycle, however, it returned a 403 Incapsula response for a browser-like profile and redirect-limit failures for bot profiles. That means it should not be linked as a clean source in the public article. It can be mentioned as a controlled official lookup that users may access manually, with a warning that access, terms and automation are constrained.

DBD Biz Regist, DataWarehouse+ service pages, DBD business-data services and the DBD online service gateway are better as workflow context. They explain registration and business-data services, but they do not replace Open-DBD dataset evidence. In a source matrix, they should sit below the dataset routes and carry explicit access-model labels.

DBD certificate verification

DBD’s English certificate verification route is useful for validation. It supports a narrow use case: checking certificates or extracts by reference. It is not a complete search index and not a bulk company dataset. In a normalized product, this belongs in a document-verification or source-evidence layer rather than the base company master table.

SEC iDISC, SET and Bank of Thailand

Thailand’s capital-market and financial-supervision sources are useful but partial. SEC iDISC listed-company profiles cleared strict checks and can support issuer-level enrichment. SET securities-list evidence is a listed-market layer with market-data terms and should remain controlled/contextual unless final publication QA confirms clean use. Bank of Thailand financial-institution lists can enrich supervised financial entities. None of these sources represent all Thai companies.

Revenue Department, procurement and IP routes

Revenue Department VAT search, Thai e-GP procurement and IP search are practical manual research tools, but they carry stronger limitations. Tax identifiers may involve privacy-sensitive or lawful-use constraints. Procurement suppliers are a subset tied to public-sector activity. IP owners are tied to trademark, patent or design activity and may include individuals. These routes are useful for enrichment and verification only when the business purpose and source terms are clear.

GLEIF LEI records for Thailand

GLEIF provides a clean public API and high-quality legal-entity identifiers for Thai entities that have LEIs. It is valuable for cross-border matching, bank and fund counterparties, issuer groups and multinational relationships. Coverage is sparse relative to the full Thai business population, so LEI should be an enrichment column, not a registry substitute.

Practical manual, API and bulk options

Manual lookup workflow

Start with DBD authority and Open-DBD dataset pages to confirm the official source family.
Use the Open-DBD juristic-person registration dataset as the base evidence route where current source checks pass.
Use DBD certificate verification only when an extract or certificate reference must be validated.
Treat DataWarehouse as a manual controlled lookup, not as a link-safe bulk source.
Add SEC iDISC, Bank of Thailand and GLEIF only when the entity appears in those partial layers.

API or bulk workflow

The practical programmatic route is Open-DBD first. Before ingestion, verify the dataset resource URL, format, licence label, update date and any API endpoint associated with the dataset page. Store the dataset-level metadata next to each ingestion job. Avoid scraping DataWarehouse while it returns bot-protection behavior and while automation rights remain unclear.

Commercial contact-data workflow

Company identity data and contact data are different products. Registry or dataset access may support entity verification, market sizing and CRM enrichment, but it does not create a lawful basis for cold outreach. For English and international contact-data workflows, route strategic demand to CompaniesData.cloud and keep suppression, consent, legitimate-interest analysis and channel rules separate from the official-source article.

Missing data gaps

Beneficial ownership: no clean public beneficial-ownership dataset was verified in this cycle.
Full historical events: Open-DBD dataset pages do not automatically prove complete event history, document availability or all past filings.
Field-level reuse: each dataset resource still needs field, licence and update-date capture before bulk reuse claims.
Contact data: officer names, addresses, email addresses or phone fields require privacy and marketing-law review before any outreach use.
Subsets: SEC, SET, Bank of Thailand, procurement, VAT, IP and LEI sources cover only parts of the economy.
Language and transliteration: Thai and English names, addresses and activity labels need careful normalization to avoid false matches.

Recommended data model

Company core: DBD registration number, legal name, normalized Latin/Thai name fields, legal form, status, registration date and source timestamp.
Source provenance: source family, URL, access date, dataset update date, licence label, resource format, crawler status and confidence score.
Address and geography: raw Thai address, normalized address, province, district, postcode and geocoding confidence.
Activity and sector: official activity codes where present, translated labels, higher-level sector buckets and source confidence.
Documents and verification: certificate reference, document type, verification route and evidence URL.
Enrichment overlays: SEC/SET listing flags, Bank of Thailand supervised-entity flags, LEI identifiers, procurement participation and IP ownership.
Privacy and lawful-use flags: natural-person involvement, contact field sensitivity, marketing-use restriction and suppression status.

CompaniesData normalization and enrichment value

Thailand illustrates why official data still needs a normalization layer. The official source stack is split across DBD datasets, DBD services, regulators, market-data sources, financial-sector lists and global LEI records. Names may appear in Thai script, English transliteration or mixed forms. Addresses may be formatted for local use rather than analytics. Source routes can be clean one week and challenged the next.

CompaniesData can add practical value by preserving source provenance, standardizing entity names, mapping activity fields, deduplicating branch or alias records, connecting DBD data to LEI and listed-company overlays, and separating company identity from contact-data permission. A buyer does not just need source URLs; they need a maintained model that explains which fields are strong, which fields are partial, and which fields require lawful-use review.

For international users, CompaniesData.cloud is the strategic place to request a Thailand dataset sample or discuss compliant enrichment. That keeps the article focused on official data and avoids turning the page into a competitor directory for contact lists.

Reuse checklist

Official-source priority: use DBD and Open-DBD before non-official aggregators.
Licence capture: record the licence or reuse note shown on each dataset page at ingestion time.
Update preservation: store update dates and access dates for every source family.
No endorsement: do not imply DBD, SEC, BOT, SET, GLEIF or any Thai authority endorses a derived dataset.
No blocked scraping: do not automate DataWarehouse while strict probes return bot-protection behavior.
No subset inflation: label procurement, regulator, exchange, VAT, IP and LEI layers as partial.
Privacy controls: flag natural-person, officer, tax and contact fields for separate lawful-use review.
Marketing separation: treat contact-data products as a separate compliance workflow from registry reuse.

Grouped Resource Pack

Core DBD and Open-DBD

Department of Business Development official company registry authority; official portal / services / registry authority.
Open-DBD portal official DBD open-data portal; CKAN/OpenD public data catalogue.
Open-DBD active juristic-person group official DBD dataset group; dataset group / public catalogue.
Open-DBD juristic-person registration dataset official juristic-person dataset; public JSON dataset and download route.
Open-DBD juristic-person count dataset official juristic-person statistics dataset; public JSON statistics dataset and download route.
DBD English certificate verification official certificate verification; certificate-reference verification.
DBD Biz Regist official digital registration service; online registration / service portal.
DBD DataWarehouse+ service page official service explainer; service page / DataWarehouse context.
DBD business data services category official service category; service category / business data services.
DBD online services for juristic persons official juristic-person service gateway; online service gateway.
Thai SEC iDISC listed company profiles listed-company disclosure search; public disclosure search.
Bank of Thailand financial institutions list financial institution list; official list / supervised financial institutions.
GLEIF LEI records for Thailand LEI API; public API.

Held or manual-only routes

DBD DataWarehouse: official controlled lookup, currently blocked in strict source QA.
General data.go.th and DGA pages: useful context when accessible, but noisy in this cycle compared with Open-DBD.
Thai e-GP, Revenue VAT, DIP and SET: enrichment routes with subset, privacy or market-data limitations.

FAQ

What is the best starting point for Thailand company data?

Start with DBD as the authority and Open-DBD as the clean dataset discovery route. The Open-DBD juristic-person registration dataset is stronger evidence for reusable company-data analysis than a blocked DataWarehouse interface.

Is DBD DataWarehouse still useful?

Yes, but as a controlled manual lookup route. In this cycle it did not clear strict source-live QA, so the public article should not frame it as a clean open bulk source.

Does Thailand provide a complete free company-register API?

This article verifies official DBD dataset pages, but it does not verify unrestricted all-field API reuse for every company-register use case. The safer claim is medium API/bulk confidence through Open-DBD, subject to dataset-level terms and final QA.

Can SEC, SET or Bank of Thailand data replace DBD?

No. Those sources are valuable for listed or regulated entities, but they cover subsets. They should enrich DBD-based company records rather than replace the registry layer.

Can public Thai company data be used for cold email?

No automatic permission follows from public access. Email, phone, officer, tax and procurement fields need separate lawful basis, suppression logic and contact-data compliance review.

What does CompaniesData add for Thailand?

CompaniesData adds normalized names, identifiers, addresses, activity labels, source provenance, update tracking, enrichment matching and lawful-use flags so users can work with a maintained dataset rather than scattered portals.

Official sources used in this article

Department of Business Development official company registry authority; official portal / services / registry authority.
Open-DBD portal official DBD open-data portal; CKAN/OpenD public data catalogue.
Open-DBD active juristic-person group official DBD dataset group; dataset group / public catalogue.
Open-DBD juristic-person registration dataset official juristic-person dataset; public JSON dataset and download route.
Open-DBD juristic-person count dataset official juristic-person statistics dataset; public JSON statistics dataset and download route.
DBD English certificate verification official certificate verification; certificate-reference verification.
DBD Biz Regist official digital registration service; online registration / service portal.
DBD DataWarehouse+ service page official service explainer; service page / DataWarehouse context.
DBD business data services category official service category; service category / business data services.
DBD online services for juristic persons official juristic-person service gateway; online service gateway.
Thai SEC iDISC listed company profiles listed-company disclosure search; public disclosure search.
Bank of Thailand financial institutions list financial institution list; official list / supervised financial institutions.
GLEIF LEI records for Thailand LEI API; public API.