# Verify email of the authorised user

The second step in verifying the authorised user's email. The randomly generated code sent to the authorised user via
email, using the *authorisedUserEmailVerificationCodeSend* operation, is submitted here to verify the authorised user's email.
This is needed as part of the verification process for basic due diligence.
*Note that on the Sandbox Environment, the `verificationCode` is always set to "123456".*

Endpoint: POST /users/verification/email/verify
Version: v3
Security: api-key

## Request fields (application/json):

  - `email` (string, required)
    E-mail Address of the user

  - `verificationCode` (string, required)
    A randomly generated one-time use code used to verify the user's email address or mobile number.

## Response 400 fields (application/json):

  - `message` (string)
    When present helps to identify and fix the problem.

  - `syntaxErrors` (object)
    Is returned as part of an HTTP error response whenever a syntax error is detected. A list of the fields together with their syntax error will be provided.

  - `syntaxErrors.invalidFields` (array)

  - `syntaxErrors.invalidFields.params` (array)

  - `syntaxErrors.invalidFields.fieldName` (string)

  - `syntaxErrors.invalidFields.error` (string)
    Enum: "REQUIRED", "HAS_TEXT", "REQUIRES", "SIZE", "RANGE", "IN", "NOT_IN", "REGEX", "EXACTLY", "AT_LEAST", "AT_MOST", "ALL_OR_NONE"

## Response 403 fields (application/json):

  - `errorCode` (string)
    Enum: "INSUFFICIENT_PERMISSIONS"

## Response 409 fields (application/json):

  - `errorCode` (string)
    Enum: "VERIFICATION_CODE_INVALID"

## Response default fields (application/json):

  - `code` (string)

  - `message` (string)