IDVB is a lightweight endpoint used for basic identity verification based on NIK (National Identity Number), full name, and optionally date of birth. This service offers a fast and cost-efficient way to confirm if a user's data matches official government records.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Supported Verification:
- Verifies the user’s NIK, Full Name, and Date of Birth (DOB).
- IDV-B Performs only data verification, excluding selfie verification. This verification is solely based on matching the user’s NIK, Full Name, and DOB against citizenship records. For detailed pricing information, please contact BOIVA directly.
Request Parameters
| Key Parameters | Data Type | Description | Required |
|---|---|---|---|
| Authorization | String | Public Access Token | Yes |
| type | String | Supported type verification. Use IDVB | Yes |
| ktp | String | User's NIK (ID Number) to be verified against citizenship data | Yes |
| fullname | String | User's fullname to be verified against citizenship data | Yes |
| birth_date | String | Format: yyyy-mm-dd. If omitted, derived from NIK | Optional |
⚠️ If birth_date is not sent, the system will derive it from the NIK. If there’s a mismatch with official records, the response may include normalized = true
Response Parameters
| Field | Type | Description |
|---|---|---|
ktp | Boolean | Whether the NIK matches government records |
fullname | Boolean | Whether the full name matches government records |
birth_date | Boolean | Whether the birth date matches (or is derived and matches) |
normalized | Boolean | true if the date of birth was derived from NIK and did not match |
Understanding
normalizedThe normalized field indicates a potential discrepancy between the user-provided or system-derived birth date and the official government records.
This situation may arise when:
- The population registry has updated or corrected a citizen's birth record (e.g., from Dukcapil).
- The client does not send a birth_date, and the system attempts to derive it from the NIK.
- The inferred date based on the NIK structure differs from the actual official birth date.
ℹ️ Statistically, this occurs in approximately 6–8% of verification cases and is considered normal, especially for older or previously migrated registry data.
Example Scenario:
You send only NIK and Full Name without birth_date.
The system derives the birth date from NIK → compares it to official data → mismatch → normalized = true.
Decision Table
| NIK Match | Fullname Match | Birth Date Sent | Birth Date Match | normalized |
|---|---|---|---|---|
| ✅ | ✅ | ❌ | ❌ (derived) | true |
| ✅ | ✅ | ✅ | ✅ | (no return) |
| ✅ | ✅ | ✅ | ❌ | (no return) |
| ✅ | ✅ | ❌ | ✅ (derived) | false |