SDKs

Xident provides SDKs for every layer of your stack. The browser SDK triggers the verification flow, server SDKs verify tokens on your backend, and mobile SDKs embed verification natively in your apps.

How It Works

  1. 1. Client starts verification — Browser or mobile SDK redirects the user to verify.xident.io
  2. 2. User completes verification — Liveness, age recognition, and/or document check happen on the Xident platform
  3. 3. Callback with token — User is redirected back to your site with a single-use token
  4. 4. Server verifies token — Your backend calls the Xident API (or uses a server SDK) to verify the token and get results

Client SDKs

Client SDKs run in the user's browser or mobile app. They handle triggering the verification flow and receiving the callback.

SDK Package Status Description
JavaScript @xident/loader Available Browser SDK — script tag or npm. ~2KB minified.
Android io.xident:sdk Coming Soon Native Android SDK for Kotlin/Java apps.
iOS Xident Coming Soon Native iOS SDK for Swift/SwiftUI apps.

Server SDKs

Server SDKs wrap the Xident REST API for token verification, usage queries, and webhook signature validation. Use these on your backend after the client-side flow completes.

SDK Package Status Description
Node.js @xident/node Coming Soon TypeScript-first SDK for Node.js, Deno, and Bun.
Python xident Coming Soon Async-ready SDK for Python 3.9+.
Go github.com/xident/xident-go Coming Soon Idiomatic Go SDK with context support.
PHP xident/xident-php Coming Soon PHP 8.1+ SDK with PSR-18 HTTP client support.

Don't See Your Language?

All Xident functionality is available through the REST API. You can verify tokens with a single HTTP call from any language:

curl -X POST https://api.xident.io/api/v1/verification-tokens/verify \
  -H "X-API-Key: sk_live_your_secret_key" \
  -H "Content-Type: application/json" \
  -d '{"token": "tok_xxx"}'

Next Steps