Developer platform

Ship verification in an afternoon.

A REST API, server SDKs, and webhooks — with sandbox credentials that behave like production and documentation written by the people who built the endpoints.

Get sandbox access Compare integration paths

The platform

Four things to integrate against.

No bespoke onboarding, no proprietary protocol to learn. If you have shipped against a payments API, this will feel familiar.

REST APIs

Simple, versioned endpoints

SDKs

Native libraries, major stacks

Webhooks

Real-time verification events

Docs & examples

Copy-paste quickstarts

A verification, end to end

One request, one consent prompt, one signed answer.

You ask for the narrowest set of attributes your product needs. The person approves in their wallet. You get claims, not document images.

RequestPOST /v1/verify

curl -X POST https://api.trueid.me/v1/verify \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "credential_id": "tid_8fK2mQ",
    "attributes": ["full_name", "date_of_birth", "kyc_status"]
  }'

Response200 OK

{
  "verified": true,
  "matched_source": "NIMC",
  "elapsed_ms": 1180,
  "attributes": {
    "full_name": "Amina Okafor",
    "date_of_birth": "1994-03-12",
    "kyc_status": "passed"
  },
  "consent": {
    "granted_at": "2026-07-29T09:14:22Z",
    "scope": "one_time"
  }
}

Sandbox keys return the same shape as production, including the failure paths — mismatched name, expired document, and manual review all have fixtures you can trigger on demand.

Quickstart

From key to first verified user.

Self-serve from the dashboard. There is no sales call between you and a working integration.

See hosted, QR, and USSD paths

Create a sandbox key

Self-serve from the dashboard. No sales call to start building.

Request a verification

POST the credential ID and the attributes you actually need.

Handle the consent prompt

The user approves in their wallet; you receive the result.

Subscribe to webhooks

Get notified on revocation, re-verification, and status changes.

Endpoints

POST/v1/verify

Request attributes from a credential, subject to user consent

GET/v1/credentials/:id

Check credential status, assurance tier, and issuance date

POST/v1/sessions

Start a hosted verification flow and receive a redirect URL

GET/v1/consents

List active consents your application holds

DELETE/v1/consents/:id

Release a standing consent your application no longer needs

POST/v1/webhooks

How we treat the API

An identity API you can depend on for years.

Verification sits in your onboarding critical path. Breaking it quietly is not an option we allow ourselves.

Commitments

Versioned endpoints with a published deprecation policy
Idempotency keys on every write, so retries are safe
Errors that name the field and the fix, not just a status code
Sandbox fixtures for every failure path, including manual review

Build your first verification today.

Sandbox credentials are self-serve. Talk to us when you are ready for production keys.

Get sandbox access Talk to engineering