Identity Verification API

An identity verification API built for the moment of action.

Most identity APIs verify a document once at onboarding. The Confrmo API verifies the human at runtime, every time it matters: at login, at payment, at approval, at document release. One call returns approve, step up or block, together with a signed, audit-ready record.

Book a demo See it live

What the API verifies

Each verification weighs facial recognition across 760+ micro-features, active and passive liveness, device trust, location, time and session behaviour against your policy. You decide the threshold per action, so a newsletter login and a seven-figure payment approval can demand different levels of assurance.

Designed for developers

REST endpoints with predictable JSON, webhooks for asynchronous decisions, SDKs for web, iOS and Android, and a WordPress plugin for teams who never want to touch the API directly. Authentication uses scoped API keys and every response is signed.

Beyond people: assets and ownership

The same platform exposes Ledger APIs for registering assets, issuing certificates and verifying ownership, so identity and ownership share one integration and one audit trail.

Common questions

What teams ask first.

How long does integration take?

A first verification flow is typically live in under a day using the web SDK. Direct REST integration adds policy configuration but follows the same pattern.

What does a verification response contain?

A decision (approve, step up or block), the signals that informed it, a signed proof token and an audit reference you can store or forward.

Is there a sandbox?

Yes. Test keys exercise the full flow against test identities before you go live.

Related Identity SDK Developer Authentication Verification Platform Developer Platform Security & Compliance

See it on your own use case.

Thirty minutes with the team, mapped to your product and your risk.

Book a demo Open Ledger