BOIVA Developer Hub

Integrate identity verification with confidence

Quickstarts on boiva.id, exact endpoint contracts in the canonical ReadMe API reference.

Quickstart

From credentials to your first verification

BOIVA exposes one token endpoint and one identity-verification endpoint. The product code controls which documented inputs and signals apply.

Integration path

Use sandbox first. Keep credentials on your server and never ship them in browser or mobile code.

Step 1

Get sandbox credentials

Obtain a Client ID and Client Key from the BOIVA team.

Step 2

Generate a public token

Call GET /b2b/v0/token with X-Client-Id and X-Client-Key.

Step 3

Send a verification

POST to /b2b/v1/identity-verification with type set to IDVB, IDVS, or IDVC.

Step 4

Prepare production

Complete sandbox testing, then switch the base URL and credentials for production.

Your first two requests

Copy-safe placeholders; replace them only in a server-side environment.

1. Generate a one-hour public access token

curl --request GET 'https://sandbox.boiva.id/b2b/v0/token' \
  --header 'X-Client-Id: {client-id}' \
  --header 'X-Client-Key: {client-key}'

2. Send an IDVB request

curl --request POST 'https://sandbox.boiva.id/b2b/v1/identity-verification' \
  --header 'Authorization: {public-access-token}' \
  --header 'Content-Type: application/json' \
  --data '{"type":"IDVB","ktp":"{nik}","fullname":"{full-name}"}'

Continue to authentication

IDVB

Basic data verification

NIK and full-name matching, with optional birth date. No selfie required.

API contract

IDVS

Data verification with selfie

Adds a required Base64 selfie to identity-data verification.

API contract

IDVC

Comprehensive verification

Combines identity, selfie, and liveness signals for a layered flow.

API contract

Production checklist: finish sandbox testing, obtain production credentials, and change the API base from sandbox.boiva.id to api.boiva.id. Keep the credentials environment-specific.