Thai Company Data API (eKYB)
Returns a Thai company's or partnership's registration record from its 13-digit registration number: status, capital, industry, address, directors, financial statements and a credit risk assessment.
The database holds 1,751,616 juristic persons from the Thai company register (27 October 2026), each with its own date in dataAsOf. The data is information the Department of Business Development publishes, collected and stored by iApp; iApp is not a government agency and does not act for the Department. Each answer names its source in meta.provenance. A lookup by registration number reads that database and answers in under a second, and a search by company or person name within 3 seconds. Call the database first. Only for a company it does not have, such as one registered in the last few days, the live endpoints fetch the latest register at the time of the call and save the company to the database, so later lookups find it at the database price.
- Price2 ICper request
- Served26.6Kcalls
- By registration number
- By company name
- Director
- Latest register (live)
Every answer is for internal business decisions only; it is not a company certificate and is not legal evidence (meta.notice). Before the first call, accept the eKYB terms once for your account, on the API Keys page or in the try-it.
Request
GET with the registration number in the path; POST with JSON for the batch. A company is identified by its 13-digit registration number (เลขทะเบียนนิติบุคคล), which is also its tax ID.
Headers
apikeystringrequiredapikey header (x-api-key and Authorization: Bearer YOUR_API_KEY also work), never in the URL, where browser and proxy logs keep it: a key in the query string is refused with 401.Path
company_idstringrequired0135556015413. A number with a wrong check digit is refused before anything is billed.Query
as_ofstring/snapshot: a date, 2026-09-30, meaning the whole day in Thai time, or an ISO 8601 date and time with the offset URL-encoded, 2026-09-30T12:00:00%2B07:00 (a time without an offset is Thai time). Any other form, such as 2026/09/30, is refused with 400 and details.reasoninvalid_format; a Buddhist-era year such as 2569-09-30 with buddhist_era_year; a date after today in Thai time with future_date and today in details.latest. Without it, or with it empty, the current version.nameprovincestatustsicstring/company/search: name, part of the Thai name, is required; province, status and tsic are optional filters, any of them or none. A province is resolved even when misspelled; the status is in Thai as the register writes it, ยังดำเนินกิจการอยู่, ร้าง or เลิก, or in the register's English, Operating, Defunct or Dissolution (any other value returns 400 with the accepted ones in details.allowed and details.allowedEnglish); tsic is a 5-digit industry code, 62022. Without all three filters the name needs at least 3 letters or digits in a row with no Thai tone mark between them: ปตท works, น้ำ does not, because the tone mark splits it (400 with name_too_short). With all three, 2 characters are enough. Matches the name partially first, then by similarity. English names are not searched here: use /live/v1/company/search.namestring/person/search: a person's name in Thai, with or without the title; at least 2 characters must remain once titles and ranks are removed (นาย alone returns 400 INVALID_REQUEST). A common name can match several hundred people: page through them with limit and offset.namelimitstring/live/v1/company/search: name, required, part of the company's name in Thai or English, at least 2 characters; limit, how many matches to return, default 10, at most 1,000, or all. POST takes the same two as JSON, {"name": "ไอแอพพ์", "limit": 20}.limitoffsetstring400 with offset_too_large), as whole numbers in plain digits (1e2 or 020 returns 400; an empty value is the same as none). On /person/search they count people, not companies.Body
idsfieldsbody/batch: {"ids": ["0135556015413", "..."], "fields": "summary"}, up to 50 numbers and 16 KB. summary returns name, province, industry code and status for each; full returns the whole record.| Endpoint | Returns | Price |
|---|---|---|
GET /ekyb/v1/company/{company_id} | The registration record | 2 IC |
GET …/{company_id}/financial | Financial statements for up to five fiscal years, and the filing status | 1 IC |
GET …/{company_id}/risk | 10 red-flag rules and a 0 to 100 risk score | 2 IC |
GET …/{company_id}/snapshot | The record as it stood on a date | Free |
POST /ekyb/v1/company/batch | Up to 50 companies in one call | 2 IC per company found |
GET /ekyb/v1/company/search | Companies by Thai name, narrowed by province, status or industry if given | 1 IC when anything is found, otherwise free |
GET /ekyb/v1/person/search | The companies where a person is a director or partner | 2 IC when anything is found, otherwise free |
GET /ekyb/live/v1/company/{company_id} | The record, fetched from the latest register now | 4 IC |
GET /ekyb/live/v1/company/{company_id}/risk | The risk assessment on a live fetch | 6 IC |
GET or POST /ekyb/live/v1/company/search | Companies by name, Thai or English, searched in the latest register now: registration numbers, status, province and the latest figures | 2 IC when anything is found, otherwise free |
Only a successful response is billed: an error, a company not found and an empty search cost nothing. A live lookup also adds or refreshes the company in the database before it answers, so later lookups find it at the database price. Use a live endpoint when the database answers 404 COMPANY_NOT_IN_DB or a search finds nothing.
Response
Every success is {"status": "success", "data": ..., "meta": ...}. The panel shows the registration record.
idnamenameEngstringname is the register's own field, without the entity type in front (ไอแอพพ์เทคโนโลยี จำกัด); /financial, /risk and the searches give the full registered name (บริษัท ไอแอพพ์เทคโนโลยี จำกัด).typeOfEntityoperatingStatusstringtypeOfEntityEng and operatingStatusEng.registrationDateISOstringregistrationDate gives it in Thai, 08 ส.ค. 2556.registerCapitalpaidCapitalnumber72005040437.5.tsicCodetsicCodeLatesttsicstring, objectaddressaddressDetailstring, objectdirectorspartnersmanaging_partnersarraytitle, firstName and lastName. A company has directors; a partnership has partners.authorized_signatorystringhistoryChangeNamehistoryChangeCapitalarraysubmittedFiscalYearsarraymeta.provenanceobjectregistration, directors and financial, each dbd_public_website (information the Department of Business Development publishes, collected by iApp), and collectedBy. It is not meta.source, which names the layer that answered.meta.noticestringAccept-Language: en, English: data as of dataAsOf, for internal business decisions only, not a company certificate or legal evidence. On /risk it adds that the score is iApp's own calculation, not credit advice.directors_hiddenpersons_redactedboolean, numberdirectors_hidden: true when the account has never bought credits: directors, partners and the signatory text are empty. persons_redacted counts the names left out at the request of the person concerned.meta.sourcestringredis or db, read from the database's cache or the database itself; dbd, fetched live from the register.meta.dataAsOfstringmeta.last_seen_dataAsOf is when it was last read from the register, and meta.updated_dataAsOf when its content last changed.Financial statements, risk, searches and batch
/financial. Read financialStatus before the numbers: ok, statements filed; never_submitted, the company has never filed, which is a definite answer; expected_but_missing, statements should exist but could not be retrieved yet, which must not be read as "no statements"; fetch_error, retrieval failed. summary gives the latest year's revenue, profit or loss and total assets; financial holds the balance sheet, income statement and ratios by year.
/risk. risk_score runs from 0 to 100 and higher means riskier; it is not a credit bureau score. risk_level is low below 20, medium from 20 and high from 50. Each raised rule is in risk_flags with its code, severity, weight and the evidence. A rule that could not be evaluated, for lack of statements for instance, is listed in risk_coverage.unavailable: no flag is not the same as checked and clean.
| Rule | Raised when | Weight |
|---|---|---|
INACTIVE_STATUS | The status is ร้าง, เลิก, เสร็จการชำระบัญชี, ล้มละลาย or พิทักษ์ทรัพย์ | 40 |
NO_FILING_2Y | No statements for 2 consecutive years (15 if the company has never filed) | 25 |
NEGATIVE_EQUITY | Shareholders' equity is negative | 25 |
LOSS_3Y | A loss in 3 consecutive years | 20 |
DIRECTOR_LINKED_STRUCK_OFF | A director or partner sits on 3 or more struck-off companies | 15 |
PEER_LEVERAGE_TSIC | Debt to equity (D/E) above 4; not evaluated when equity is zero or negative | 10 |
REVENUE_DROP_YOY | Revenue down 30% or more on the year before | 10 |
FREQUENT_CHANGES | 2 name changes or 3 capital changes within 3 years | 10 |
CAPITAL_VS_REVENUE_LOW | Registered capital under 1% of revenue, for revenue of 10 million baht or more | 5 |
YOUNG_HIGH_CAPITAL | Under 2 years old with registered capital of 5 million baht or more | 5 |
DIRECTOR_LINKED_STRUCK_OFF is common in large groups, whose directors sit on many boards; on its own it leaves a company at low. The live risk endpoint evaluates it on the directors it has just fetched, against the other companies in the database, so a live and a database score of the same record agree; if the database does not answer within 2 seconds, the rule is listed as unavailable for that call.
/company/search and /person/search. data is an array; meta carries totalItems, returned and hasMore (totalPersons and returnedPersons on /person/search). Nothing found is HTTP 200 with an empty array. On /company/search, meta.filters lists the filters used, and meta.complete says whether the list is complete: a name that matches very many companies, such as ไทย without filters (about 100,000), is read up to 5,000 matching companies, so the list is partial, totalItems is a lower bound, meta.hint asks for more of the name or a filter, and the order (most similar first, then highest revenue) is within the companies read. On /person/search, meta.complete works the same way: a name that matches very many people, such as a short common part of a name (ศรี), is read up to 10,000 matching entries, so the list is partial, totalPersons is a lower bound and meta.hint asks for more of the name; the person whose full name matches exactly is always listed first, and each person's totalCompanies is exact. Each person comes with their companies, at most 50, each with the role: director, partner or managing_partner. A name is not an identity: the register publishes no ID card numbers, so two people with the same name are one entry, and meta.confidence is always name_only.
/live/v1/company/search. Searches the latest register by name at the time of the call, in Thai or English. data.results lists the matches, each with company_id, name, nameEng, typeOfEntity, operatingStatus, tsicCode, tsicDescription and province, and the latest filed year's registerCapitalTHB, totalRevenueTHB, netProfitTHB, totalAssetsTHB and shareholderEquityTHB as text with commas, for the Buddhist-era fiscalYear. data.totalItems counts every match in the register and truncated is true when there are more than returned. Results always start from the first match, so narrow the name rather than page. When nothing matches, the search is retried without บริษัท, จำกัด and the like, and keywordUsed gives the words that matched. Nothing found is 404 COMPANY_NOT_FOUND and costs nothing. The register returns 10 names a page, so every 10 not yet fetched adds about a second; the same search within an hour is answered from a cache in under 0.1 seconds. For the full record, look up the company_id with /ekyb/v1/company/{company_id}; if that returns 404 COMPANY_NOT_IN_DB, call /ekyb/live/v1/company/{company_id}, 4 IC, nothing billed if the register has no such company. The search, shown in part:
{
"status": "success",
"data": {
"keyword": "บริษัท ไอแอพพ์เทคโนโลยี จำกัด",
"keywordUsed": "ไอแอพพ์เทคโนโลยี",
"totalItems": 1,
"returned": 1,
"limit": 10,
"truncated": false,
"results": [
{
"company_id": "0135556015413",
"name": "ไอแอพพ์เทคโนโลยี จำกัด",
"nameEng": "I APP TECHNOLOGY COMPANY LIMITED",
"typeOfEntity": "บริษัทจำกัด",
"operatingStatus": "ยังดำเนินกิจการอยู่",
"tsicCode": "62022",
"province": "ปทุมธานี",
"registerCapitalTHB": "31,500,000.00",
"totalRevenueTHB": "24,779,480.39",
"netProfitTHB": "241,556.87",
"fiscalYear": "2568"
}
]
},
"meta": { "fetchedAt": "28/10/2026 11:34:32", "requestId": "bbb26a9418635f91cbedde9d297d5997" }
}
/batch. data lists the numbers in the order sent, each with found and, when not found, a reason; meta counts requested, found, notInDb, invalid and duplicates. Only found companies are billed.
/snapshot. The record has the same shape as a lookup. History is kept from 28 August 2026, one version each time the record changes: meta.versions counts them, meta.historyFrom is the earliest date this company can be asked for, and meta.validFrom and meta.validTo give the period the returned version was current.
Details
Errors
An error is {"status": "error", "error": {"code", "message", "details", "requestId"}}. Act on code; the wording of message may change.
| HTTP | code | Meaning |
|---|---|---|
| 400 | INVALID_JURISTIC_ID | Not 13 digits, or the check digit is wrong; details.reason says which |
| 400 | INVALID_REQUEST, BATCH_TOO_LARGE | A parameter is missing or invalid (details names it: reason is invalid_format or invalid_date for as_of, future_date for an as_of after today, unknown_status for a status the register does not use, name_too_short when fewer than 2 characters of a person's name remain without the title or a company name without all three filters has no 3 letters or digits in a row, offset_too_large for an offset over 10,000, or nul_character for a NUL character, %00, in a parameter), or more than 50 numbers |
| 400 | KEYWORD_REJECTED | Live name search: the register refuses a term that is too broad, such as บริษัท. Use a more specific name |
| 403 | EKYB_TERMS_REQUIRED | The account has not accepted the eKYB terms in force; details.required, details.accepted and details.acceptUrl say which and where |
| 403 | PAID_ACCOUNT_REQUIRED | /person/search from an account that has never bought credits |
| 404 | COMPANY_NOT_IN_DB | Not in the database. Check the number; a company registered in the last few days can be fetched with the live lookup |
| 404 | COMPANY_NOT_FOUND | Live lookup or name search: the register has no company with this number or name. /financial: the database records that the register has no company with this number |
| 404 | SNAPSHOT_NOT_FOUND | The date is before the record's history begins; details.historyFrom gives the first date |
| 404 | ENDPOINT_NOT_FOUND | No such path under /ekyb. A company number made only of letters, hyphens or spaces, such as abc, is read as a path, so it gets this code rather than INVALID_JURISTIC_ID |
| 405 | METHOD_NOT_ALLOWED | The path does not take this method, such as GET on /batch; the Allow header lists the methods it takes. HEAD works wherever GET does and is billed the same |
| 413 | PAYLOAD_TOO_LARGE | A batch body over 16 KB |
| 429 | DAILY_COMPANY_QUOTA | The account has looked up its 1,000 different companies for the day; details.limit, details.used and details.resetsAt (midnight, Bangkok time). A company already looked up that day still answers |
| 429 | SERVICE_BUSY | Live endpoints: the queue of register fetches is full. Retry after details.retryAfterSeconds (unlike the gateway's 429, which has no code) |
| 502 | UPSTREAM_ERROR, UPSTREAM_INCOMPLETE | Live endpoints: the register answered with an error or sent incomplete data, which is not stored. Retry later |
| 503 | REQUEST_TIMEOUT, UPSTREAM_RATE_LIMITED | Live endpoints: the register did not answer in 25 seconds (60 for a live name search asking for more than 100 results) or is limiting requests. Retry after details.retryAfterSeconds |
| 503 | UPSTREAM_AUTH_FAILED | Live endpoints: the connection to the register failed for the moment. Retry after details.retryAfterSeconds |
| 503 | DB_TIMEOUT, DB_UNAVAILABLE | Database endpoints: the search took over 3 seconds (a very short name, for example) or the database is unavailable. It does not mean there is no data: retry, or give a longer name |
| 500 | INTERNAL_ERROR | An internal error. Send the requestId to iApp |
No error is billed. An error with details.retryAfterSeconds also carries a Retry-After header. message is in Thai; send Accept-Language: en for English.
The gateway answers 401 for a missing or wrong key and 429 over the rate limit, as {"message": ..., "request_id": ...} without a code; the service's own 429s carry a code.
Limits
- Database endpoints: 100 requests a second per key. On 29 October 2026 they answered in 0.07 seconds (median), 95% within 0.10 seconds, fastest 0.05 and slowest 0.16, measured from a caller in Bangkok through
api.iapp.co.thwith the network included: 120 calls, the record, the statements and the risk of 40 companies drawn at random from the database. The service itself took 9 ms (median) of that. A search by company or person name stops at 3 seconds with503 DB_TIMEOUT, which is not billed. - Live endpoints: 30 requests a minute per key, the lookup and the risk endpoint counting together and the search separately. A live lookup took 1.0 second on 27 October 2026; when the register is slow a call waits up to 25 seconds (60 seconds for a live name search asking for more than 100 results), then returns
503with a retry time, unbilled. - Each account may look up at most 1,000 different companies a day, all endpoints together and search result rows included; a company already looked up that day does not count again. The day ends at midnight, Bangkok time. For more, write to sale@iapp.co.th.
- Accounts that have never bought credits get no person names (
directors_hidden: true) and cannot use/person/search. - Shareholder lists (บอจ.5) and beneficial owners are not included:
shareholdersanduboare empty andubo_availableisfalse.
Data handling
Using eKYB means accepting the iApp eKYB Terms of Use. In short:
- Source. Information the Department of Business Development publishes, collected and stored by iApp, as
meta.provenancestates; a live call reads the register at the time of the call. iApp is not the registrar and does not certify the data. - Permitted use. Your own internal decisions: KYB, customer due diligence, credit and supplier checks.
- Not permitted. Publishing the data, reselling it, copying it into another database, or using people's names for marketing.
- No warranty, and errors. The data is as of
dataAsOfand may differ from the register today. Report an error to support@iapp.co.th; the register itself is corrected at the Department of Business Development. - People named in the data. Directors' and partners' names are personal data, and you are the controller of what you receive. Their notice is the privacy notice for directors and partners; they can object through the request form, and a name whose objection is accepted is left out of every answer (
persons_redacted). - Logs. Each call is logged with the calling account and what it looked up, for billing, support and the prevention of misuse.