Identity Check
Confirm the person behind a NIK.
Registered name, sex and date of birth from a 16-digit NIK.
GET /v1/identity/check/:nik scope: identity:check
Key points
Why teams use Identity Check
Stop fake identities early
A made-up or mistyped NIK fails before the user reaches your product.
Pay once per identity
Results are cached encrypted, so repeat lookups never re-query the source.
Audit-ready
Every lookup is logged with key, time, outcome and cost.
How it works
From request to result
- Sign a GET request with your API key.
- The gateway verifies signature, replay window, rate limit and scope.
- Receive normalized fields and a request ID.
Billed per successful lookup, including cached answers. Invalid input, rate-limited and provider-error requests are free.
Full API reference →request · exampleGET
GET /v1/identity/check/3201••••••••0001
X-Api-Key: key_live_••••
X-Timestamp: 1757022089
X-Nonce: 9f1c••••
X-Signature: v1=••••response · example200
{
"data": {
"nama": "B••• S•••••",
"sex": "L",
"tglLahir": "••-••-1990"
},
"requestId": "5d3c…"
}FAQ
Questions
Is a repeat lookup of the same NIK billed?
Yes. It returns instantly from the encrypted cache and does not query the source again.
Is this connected to Dukcapil?
No — and we're not pretending otherwise. Identity Check runs on our own verification pipeline, independent of any government system.
Put Identity Check into production.
Request access and our team activates your account, or talk to sales about volume.
Identity Check · from Rp600Request API access