Thailand Company Registry Changes — New & Closed Businesses

Turn official Thai Department of Business Development (DBD) monthly open data into a clean, filterable change feed for newly registered and dissolved businesses.

This Actor is intentionally not a generic company lookup scraper. It is designed for sales-intelligence pipelines, market monitoring, data agents, MCP/API workflows, and recurring business-change tracking that need deterministic official registry events rather than raw portal pages.

What you can query

• changeType: new or closed
• month: latest, Gregorian YYYY-MM (for example 2026-08), or Buddhist Era YYYY-MM (for example 2569-08)
• province: optional Thai province
• entityType: optional legal-form filter
• minRegisteredCapital / maxRegisteredCapital
• objectiveKeyword: substring match against the official DBD objective code/description
• includeAddress: off by default
• limit: 1–5000 records

Example input

{
  "changeType": "new",
  "month": "latest",
  "province": "สมุทรปราการ",
  "minRegisteredCapital": 500000,
  "objectiveKeyword": "ซ่อม",
  "includeAddress": false,
  "limit": 100
}

Example output

{
  "juristic_id": "0112569000042",
  "legal_name_th": "หส.เจพี ท๊อป จูนเนอร์ การาจ",
  "change_type": "new",
  "registration_date": "2026-08-27",
  "entity_type": "ห้างหุ้นส่วนสามัญนิติบุคคล",
  "entity_type_basis": "derived_from_official_legal_name",
  "registered_capital": 500000,
  "business_objective_code": "45201",
  "business_objective": "...",
  "province": "สมุทรปราการ",
  "source": "Department of Business Development (DBD), Thailand Open Data",
  "source_url": "https://opendata.dbd.go.th/th/dataset/dataset_11_01",
  "license": "Open Data Common",
  "source_updated_at": "...",
  "retrieved_at": "...",
  "source_resource_id": "...",
  "source_resource_name": "..."
}

The example above mirrors the structure of an official DBD record. Values can change as DBD publishes new monthly resources.

Data source and provenance

Version 1 uses only official/public DBD data. The Actor tries the DBD CKAN/DataStore endpoint first, then the official Data.go.th (DGA) mirror, then the Government Data Catalog (gdcatalog.go.th) dataset published under the Department of Business Development organization. GDC metadata identifies the organization as กรมพัฒนาธุรกิจการค้า, uses Open Data Common licensing, and links the resources back to DBD/openapi infrastructure. The source boundary is fixed in code; users cannot submit arbitrary URLs. Every delivered record identifies the actual official endpoint used and includes source name, source URL, license, resource ID/name, source update timestamp when available, and retrieval timestamp.

The primary DBD packages are dataset_11_01 (new registrations) and dataset_11_02 (dissolutions). Their official Data.go.th mirror packages are dataset_11_0121 and dataset_11_0219; the Government Data Catalog mirrors are gdpublish-dataset-11-0139 and gdpublish-dataset-11-0228.

DBD publishes monthly resources. The Actor selects a resource by the expected dataset, expected Thai resource-name token, requested month, and expected column schema. This prevents a mislabeled or cross-linked resource from silently becoming output. For month=latest, the Actor may use the latest valid resource available from an official mirror when earlier official routes are unavailable. Mirrors can lag the DBD primary and each other. For an explicit month, it never silently downgrades to an older month; if that exact official month cannot be obtained, the run fails closed.

Entity type note

The monthly new/closed resources do not expose a dedicated entity-type column. In v1, entity_type is therefore derived conservatively from the official Thai legal-name prefix (บจก., บมจ., หจก., หส., or equivalent long form). Every such value is explicitly labeled with entity_type_basis = derived_from_official_legal_name. If the prefix is not recognized, the field is null; the Actor does not guess.

Address minimization

registered_office_address is omitted by default. Set includeAddress to true only when the registered office is necessary for your lawful use case.

Pricing

Pay per event (PPE) target:

• platform-managed apify-actor-start: $0.00005 per actual Actor run
• custom company-change: $0.01 per delivered company-change dataset record (primary event)
• apify-default-dataset-item: must remain removed/disabled so a delivered row is not double-charged
• platform usage pass-through to the buyer: No

The product code emits only the custom company-change event through Actor.push_data(..., charged_event_name="company-change"); it does not manually emit the platform-managed start event. Source failures and filtered/non-delivered records do not emit company-change. Active cloud PPE configuration must be verified before publication.

Limitations

• This is monthly registry-change intelligence, not a real-time government notification service.
• The DBD primary endpoint, the official Data.go.th mirror, and the Government Data Catalog mirror can update on different schedules. During upstream outages, month=latest may therefore resolve to an older valid month from the first working official route in the fixed fallback chain. Explicit month requests never silently downgrade to an older month.
• Province text is normalized for common จ. / จังหวัด prefixes; no geocoding is performed.
• The Actor does not infer creditworthiness, solvency, fraud, scam, or business-quality scores.
• No phone/email enrichment, private data collection, login/CAPTCHA bypass, or arbitrary-site scraping is performed.

Compliance disclaimer

Registry/public-business information only. This Actor is not legal advice, credit certification, due-diligence certification, or a guarantee of company quality, status, or solvency. Verify material decisions against the current authoritative registry and applicable law.