Developers

An API-first platform

Every surface FaceTrust AI ships — consumer app, Merchant Desk, Institution Console — is a thin client over one documented API. Nothing important is logic baked into a screen.

Endpoint groups

Identity linking

Validate a NIN/BVN and link it to an account with a face proof.

POST/identity/nin/validate
POST/identity/verify-face
DELETE/identity/nin

Verification

1:N identify calls and self-verification.

POST/identify
GET/identify/history
POST/identify/:referenceId/escalate

Profile & audit

Consumer profile management and the audit trail behind it.

GET/users/:id
PATCH/users/:id
GET/users/:id/export

Operators & institutions

Staff, branches, and institution-level administration.

POST/operators
GET/institutions/branches
POST/kyb/start

Analytics

Accuracy, volume, and billing, scoped to your institution.

GET/analytics/accuracy
GET/analytics/volume
GET/billing/:orgId

Authentication, by subject type

There's no single login flow — what's required to authenticate scales with what that session can do.

Consumer

Phone number + OTP, then a face proof for anything identity-linked.

Operator

Operator code + password, with a forced reset on first login.

Institution officer / branch manager

Work email + OTP + password + a face check, re-proved for sensitive actions.

Superadmin

Work email + OTP + face check + a hardware security key, with two-person approval on the most sensitive actions.

Idempotency

Mutating calls on identity linking and identify support an idempotency key, so a retried request after a dropped connection can't double-enroll or double-log a scan.

Rate limiting

Endpoint classes are rate-limited independently, with tighter per-NIN/BVN throttling on face-verify calls as a brute-force control.

Versioned endpoints

Every endpoint above is a real, versioned route — the same ones the consumer app, Merchant Desk, and Institution Console call themselves. Nothing is UI-only.

Full API reference and integration guides are available for approved institutions and merchants — reach out for access.

Ready to integrate?

Tell us what you're building and we'll get you API reference access.