BOIVA

BOIVA Developer Hub

Integrate identity verification with confidence

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

Canonical API Reference
GET /b2b/v0/token

Generate a public access token

Send your Client ID and Client Key as request headers. BOIVA returns a token scoped for identity verification and valid for one hour.

Sandbox request

This token endpoint is called without a preceding Authorization header.

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

The client identifier provided by the BOIVA team.

X-Client-Key

The client key provided by the BOIVA team.

Successful response

{
  "token": "{public-access-token}",
  "scopes": ["identity_verification"],
  "duration": 3600000
}
token

Use as the Authorization header value.

scopes

Eligible API scope.

duration

Milliseconds until expiry.

Server-side token lifecycle

  1. 01 · STORE

    Keep the Client ID, Client Key, and token out of browser bundles, mobile apps, logs, and repositories.

  2. 02 · CACHE

    Cache the token on your server and account for its one-hour validity.

  3. 03 · RENEW

    Generate a new token before expiry and handle a 401 response without exposing credentials.

Do not add “Bearer” unless your assigned API contract says so

The canonical BOIVA reference defines the Authorization parameter as the Public Access Token. Use the exact header format in your provisioned contract.

Open the canonical token reference