Create an identity verification

Creates or returns the existing legacy identity verification for a Person or Account subject. Account and Person aliases can address the same verification. Responses always retain its canonical persisted subject (Person when a Person owns the legacy identity), regardless of the alias used to create/read it. An Account request does not relabel an existing Person verification or start a separate session. The current bridge always runs the existing enhanced embedded identity flow; tier selection, additional checks, metadata, notification controls, and inline monitoring are not accepted until native V3 identity verification flows are available. Replays with the same Idempotency-Key and subject return the original verification; reusing the key with a different subject returns 409.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Request body for creating a legacy identity verification for a Person or Account subject. The current bridge always runs the existing enhanced embedded identity flow; tier selection, additional checks, metadata, notification controls, and inline monitoring are not accepted until native V3 identity verification flows are available.

subject
object
required

Subject to verify through the legacy identity-verification bridge. Relationship subjects such as Payee, Payer, and Stakeholder remain scaffolded until the native V3 subject resolver is available.

Headers
string
length between 1 and 255
^[\x21-\x7e]{1,255}$

Optional retry token. Replaying the same key with the same subject returns the original verification; replaying the key with a different subject returns 409 ResourceConflict.

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json