Developer platform
Identity verification APIs that fit your stack
Verify credentials with TENSAI readers over HID or REST, and read physical documents through the OCR API — without becoming a cryptography team.
Reader integration
Pick the path that fits your stack
Both paths drive every TENSAI reader — the TR-50 dongle, TR-100 verifier and TR-500 terminal — with the same calls.
HID API
The device appears as a standard HID peripheral. Minimal integration, no driver install — ideal for locked-down or legacy hosts.
REST API
Call the reader over HTTP. Language-agnostic and easy to embed in web front-ends or back-office services.
The shape of a verification — illustrative
# Ask the reader to run a verification (REST path)
POST /verify
{
"request": ["age_over_18", "portrait"]
}
# The SDK handles engagement, the secure session,
# selective disclosure and issuer + device checks.
# You get back a signed, validated result:
{
"status": "verified",
"attributes": { "age_over_18": true },
"portrait": "<image>",
"issuer_authenticated": true,
"device_authenticated": true
}Illustrative only — field names and endpoints are simplified. Full API references ship with your sandbox access.
Everything above is handled by the SDK — your code sees a request and a verified result.
Under the hood
What the SDK does with each check
Six steps run between your call and the result — you don't implement any of them, but it helps to know they're there.
Engagement
Holder shows a QR or taps NFC; reader and wallet open a secure session.
Request
Verifier asks for specific attributes only — selective disclosure.
Transfer
Wallet returns signed data over BLE (or online for 18013-7).
Issuer authentication
The signature is checked against a trusted issuer (IACA) chain.
Device authentication
Confirms the credential is bound to the genuine device — anti-clone.
Result
Attributes confirmed authentic, current and unaltered.
Document OCR
One POST for physical documents
Send a photo of a licence, passport or ID card; get structured, validated fields back. No templates to configure, no per-document setup.
REST API with sandbox keys — test from your terminal in minutes
Handles tilted, glare-heavy and slightly blurry phone photos automatically
Structured JSON out: fields, signatures and address overlays
Webhooks available for asynchronous workflows
Getting started
Sandbox to production in three steps
Get sandbox keys
Request sandbox access and you can call the OCR API and exercise reader flows against test data.
Build against the sandbox
Integrate the REST endpoints or the HID path, wire up your result handling, and test with your own documents.
Go to production
Swap sandbox keys for production keys. Our first production deployments each went live within about a week.
Building with hardware too? See the TENSAI reader family →
Ready to make your first call?
Request sandbox keys and we'll set you up with API access, references and a direct line to the engineers who built it.