Resolve

Beta. POST /v1/resolve accepts an exact UEN or a company name (current or former). It never silently selects a company when more than one candidate matches.

Planned base: https://api.telltale.actuans.com. Not live. Bearer token required.

Request

Send JSON with exactly one of uen or name:

POST /v1/resolve
Authorization: Bearer <api_token>
Content-Type: application/json

{"uen":"12345678A"}

POST /v1/resolve
Authorization: Bearer <api_token>
Content-Type: application/json

{"name":"EXAMPLE PTE. LTD."}

Result statuses

Every HTTP 200 body has status equal to exactly one of:

status	Meaning
resolved	One canonical company_id with scheme SG_UEN.
ambiguous	All deterministic candidates. No selected company.
not_found	Empty candidate list.

ambiguous and not_found are normal 200 outcomes, not HTTP errors. Inspect status and candidates.

Only a uniquely resolved input can become a canonical watchlist member. Later company reads require an explicit SG_UEN path value.

The response also includes source_health. Cadence is monthly.