Nani API Documentation
Verify users with document checks, liveness, and decisioning — one API, a hosted flow your users complete, and a console your team trusts.
Getting started
Create verification sessions from your backend, send users to the hosted verify_url, and receive signed webhooks when a decision is ready. Start with the quickstart, then explore the API reference.
Sandbox access requires an API key from the Nani console. Use x-api-key on server-to-server
requests — never expose keys in the browser.
Core concepts
Sessions — A single verification attempt for one end-user. Each session has a verify_url, required steps, and a final decision.
Identities — The verified person (or business) stored in your tenant vault after a successful session.
Tiers — tier1 (document), tier2 (+ liveness), tier3 (+ proof of address). Country rules determine exact steps.
Webhooks — Async notifications when sessions complete (session.approved, session.rejected, and more).