Sign in
NEWBIZFILE + MYCOID (CRS)

One API for Singapore & Malaysia
corporate data.

Connect verified entity and officer data from Singapore BizFile and Malaysia MYCOID (CRS) through one secure, consistent REST API.

🇸🇬 Singapore · BizFile🇲🇾 Malaysia · MYCOID (CRS)
Start building →Explore API
✓TLS 1.2+✓OAuth 2.0✓Unmasked officer data
Request preview SANDBOX
GET/v1/sg/entities/202612345N200 · 428ms
{
  "data": {
    "uen": "202612345N",
    "name": "LETTAGA DEMO PTE. LTD.",
    "entity_type": "PRIVATE_COMPANY_LIMITED_BY_SHARES",
    "status": "LIVE",
    "incorporation_date": "2026-01-10",
    "registered_address": {
      "street": "1 RAFFLES PLACE",
      "postal_code": "048616",
      "country": "SINGAPORE"
    }
  },
  "request_id": "req_01SGA91"
}
HTTPSTLS 1.3application/json
2jurisdictions
6focused endpoints
< 1 minto first request
24 / 7encrypted access

QUICK START

Your first request in three steps.

LETTAGA manages each registry connection. You only manage your API credentials and the company identifier.

01
⌁

Create a sandbox key

Create a test Client ID and Secret in the developer console.

Developer console →
02
</>

Request an access token

Use OAuth 2.0 Client Credentials to issue a short-lived token.

POST /oauth/token
03
→

Query registry data

Choose a jurisdiction and retrieve original entity and officer data.

GET /v1/:country/entities/:id
curl --request GET \
  --url https://sandbox-api.lettaga.ai/v1/sg/entities/202612345N \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  --header 'X-Language: en-GB'

API REFERENCE

One contract. Two registries.

Country-specific resources prevent identifier ambiguity. All responses are JSON and encrypted in transit.

Singapore / BizFile / Entity lookup

Entity lookup

Retrieve the entity's original registry profile.

GET/v1/sg/entities/{uen}

Path parameters

uenrequired
string

UEN for Singapore BizFile or registration number for Malaysia MYCOID (CRS).

Required scope

sg:entities:read
Original source data

Approved subscriptions and scopes return unmasked registry data, including officer identifiers. Response bodies are never written to application logs.

Try itSANDBOX
Response200 OK
{
  "data": {
    "uen": "202612345N",
    "name": "LETTAGA DEMO PTE. LTD.",
    "entity_type": "PRIVATE_COMPANY_LIMITED_BY_SHARES",
    "status": "LIVE",
    "incorporation_date": "2026-01-10",
    "registered_address": {
      "street": "1 RAFFLES PLACE",
      "postal_code": "048616",
      "country": "SINGAPORE"
    }
  },
  "request_id": "req_01SGA91"
}

SECURITY BY DEFAULT

Original data preserved. Access tightly controlled.

LETTAGA does not alter registry values. Encryption, authentication, authorisation and audit controls protect every request.

Security →
01

TLS encrypted

TLS 1.2 or higher protects external and internal traffic.

02

Scoped access

Entitlements are checked for every customer and API key.

03

Full audit trail

Every resource access is recorded with actor and time.

04

No payload logs

Unmasked personal data is excluded from application logs.

BUILD WITH LETTAGA

Connect Singapore and Malaysia corporate data today.

Talk to our API team