Start the applicant's identity verification
Starts an identity verification attempt for the application’s applicant and returns url, a hosted verification page. Send the applicant to it: they complete the identity check there, with no Zuba dashboard session, and the outcome reaches Zuba by webhook; read it back from GET /v2/applications//identity-verification. The link is valid until the session expires under the verification workflow’s expiry, and is returned only here, so start a new session for a new link. A new attempt replaces an earlier one, a waived outcome included, which then reads pending and no longer satisfies POST /v2/applications//submit until the attempt passes. A start is refused (409) while an attempt is still being decided by the verification provider or a reviewer, for an applicant already verified, and when the attempt changes while starting. A verified or waived outcome satisfies the identity requirement of POST /v2/applications//submit.
Authorizations
Enter Auth0 JWT token
Path Parameters
Response
The attempt's session id. Null in the sandbox, where starting a session verifies the applicant at once.
pending until the applicant completes the link and the outcome arrives; read it back from GET /v2/applications/{id}/identity-verification. verified in the sandbox, where starting a session verifies the applicant at once.
pending, verified When the attempt reached its outcome: null while it is pending, set in the sandbox, where the attempt is verified at once.
The hosted verification page for this attempt. Send the applicant to it: they complete the identity check there, and the outcome reaches Zuba by webhook. Valid until the session expires under the verification workflow’s expiry. It is returned only here and never stored, so start a new session for a new link. Null in the sandbox, where starting a session verifies the applicant at once.