Developer preview

One stable integration contract across providers.

Create a session, send an applicant through a hosted country-aware flow, and consume a signed outcome without coupling your product to each downstream verification vendor.
Book a pilotReview security
The verification flow

What the integration covers

Four contracts cover the complete verification flow, from opening a session to consuming the signed outcome.

Verification sessions

Create a tenant-scoped session against an active, immutable policy version.

Applicant access

Issue time-limited applicant links without placing identity evidence in the URL or staff interface.

Security model

Preserve policy checksums, authorization boundaries, and an auditable operational timeline.

Signed webhooks

Consume signed status events with stable event IDs, retry handling, and receiver-side deduplication.
POST /verification-sessionsSandbox
Request
  • externalReference"customer-synthetic-001"
  • policyKey"haiti-individual-starter"
  • locale"fr"
201 Created
  • id"01949456-e0e4-…"
  • status"created"
  • hostedUrl"https://app.verela.example/verify/…"
  • expiresAt"2026-07-26T12:00:00.000Z"
Field names and example values are taken from the published verela.v1 OpenAPI contract.

Current release boundary

The API is operating as a synthetic sandbox preview. Endpoint schemas, idempotency, tenant isolation, API-key scope, signed webhook behavior, and deterministic test identities are built; public partner credentials and production provider access remain gated.

Read the contract, then run it on one workflow.

The session, applicant-link, and webhook contracts are built and documented. Sandbox credentials are issued through a pilot conversation rather than self-serve.
Book a pilotStart free
Founder-led and purpose-limited. No production identity data is required for the first evaluation.