Create an identity verification

Creates or returns an open identity verification for a Person, Account, or Stakeholder. Select X-Wingspan-Account to verify an active Stakeholder using its Account-supplied Individual identity. Create one verification for each human, then resume each to obtain its separate SDK token. A representative with multiple roles uses one Stakeholder verification. No Wingspan Person login is required for this flow. For an Account with no principal, Account convenience requests resolve to the selected representative Stakeholder when available and reuse the same open verification. Unmapped legacy Business representatives retain an Account subject. An Account with a principal verifies its principal Person. Callers with Account scope can read that verification, but only that Person can create or resume it; anyone else gets 403. Existing Individual/Person aliases retain their canonical Person subject. Reads and resume of Account-owned verifications require Account scope. The identity record and vault are bound at creation. After they are replaced, resuming the earlier verification returns 409 and a new create opens a verification for the replacement identity. Private Person-owned identities require Person authorization. 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 an identity verification for a Person, Account, or Stakeholder 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

Stakeholder subjects require an authorized Account session and an active Account-supplied Individual identity. Each Stakeholder has independent sessions and results. For an Account with no principal, Account subjects resolve to the Business representative Stakeholder when available; unmapped legacy representatives retain an Account subject. An Account with a principal verifies its principal Person. Person subjects preserve their existing authorization.

Headers
string
^(?:[A-Za-z0-9_.]{22}|[a-f0-9]{24})$

Select the Account for an Account-scoped operation. A direct ServiceAccount API key MUST supply this header, and the target must be within the ServiceAccount owner's or Authorization grant's Account boundary. A Person bearer may select an Account on which it has an active Stakeholder, and an Account session may select its bound Account (or a descendant only when the session explicitly includes descendants).

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