# Start verification

Starts a new identity verification session using the specified IdRamp Identity Verifier instance.

How it works
- Provide the identityVerifierId for the IdV configuration you want to use.
- Provide a returnUrl. If verification succeeds, the user is redirected to this URL.
- customFields can carry additional key–value metadata required by your client workflow.

Successful response (200)
- Returns StartVerificationResponseDto with:
  - id: the server-generated verification session identifier.
  - status: the current session status.
  - startUrl: a URL your client/app can open to begin the provider’s verification flow.

Errors
- 401/403: missing or invalid API key, or insufficient policy.
- 422: request body failed validation (see ErrorResponse).

Auth
- Requires x-api-key with the ApiKeyPolicy.

Endpoint: POST /api/v1/verification
Version: 1.0
Security: ApiKey

## Request fields (application/json):

  - `identityVerifierId` (string, required)
    The IdRamp IdentityVerifier instance id to use for this session.

  - `returnUrl` (string,null, required)
    If present, users will be redirected to this url upon successful verification.

  - `customFields` (object,null)
    Custom fields to address client specific requirements

## Response 200 fields (application/json):

  - `id` (string,null)
    The Id of the verification session

  - `status` (string,null)
    Current status of the verficiation session

  - `startUrl` (string,null)
    Url to start a new Identity Verification session with IdV provider.

## Response 422 fields (application/json):

  - `status` (integer)

  - `message` (string,null)

  - `errorCode` (string,null)

  - `details` (string,null)

  - `timestamp` (string)

  - `diagnosticsId` (string,null)


## Response 401 fields

## Response 403 fields