> ## Documentation Index
> Fetch the complete documentation index at: https://docs.annature.com.au/llms.txt
> Use this file to discover all available pages before exploring further.

# Update a verification

<Info>
  Verification endpoints use the `/v2/` namespace. `/v1/` endpoints are deprecated and will be removed without notice to new integrators.
</Info>

Updates the details of an existing verification. This endpoint can only be used while the verification’s status is `sent`.

Only properties included in the request body will be updated. Any properties not supplied will retain their existing values.

`name` and `email` cannot be cleared. `mobile` and `mobile_otp` can be removed by sending `null`.

When a verification is updated:

* All active verification sessions are immediately expired. If the individual is currently completing the verification, their session will be forcibly closed.
* If the email address is changed, previously issued email tokens are invalidated, and a new verification email is sent automatically (unless the verification is muted).
* If the mobile number is changed to a new value, a new SMS is sent automatically (unless the verification is muted).

## Parameters

<ParamField path="id" type="string" required>
  The unique identifier of the verification to update.
</ParamField>

<ParamField path="name" type="string">
  The full name of the individual being verified.
</ParamField>

<ParamField path="email" type="string">
  The individual’s email address, used for identification and correspondence.
</ParamField>

<ParamField path="mobile" type="string">
  The individual’s mobile number, supplied in E.164 format. This number is used to send an SMS with a link to open the verification.

  Send `null` to remove the mobile number.

  While it is technically possible to use both `mobile` and `mobile_otp`, we strongly recommend using only one. Sending both the verification link and the OTP to the same device does not meet the requirements for two-factor authentication.
</ParamField>

<ParamField path="mobile_otp" type="string">
  Enables SMS-based two-factor authentication by specifying the individual’s mobile number, formatted in E.164.

  Send `null` to remove two-factor authentication.

  While it is technically possible to use both `mobile_otp` and `mobile`, we strongly recommend using only one. Sending both the verification link and the OTP to the same device does not meet the requirements for two-factor authentication.
</ParamField>

<RequestExample>
  ```bash Endpoint theme={null}
  PUT /v2/verifications/:id
  ```

  ```json Body theme={null}
  {
    "name": "Ted Annature",
    "email": "ted@annature.com.au",
    "mobile": "+61422000000",
    "mobile_otp": "+61422000000"
  }
  ```
</RequestExample>

<ResponseExample>
  ```json theme={null}
  {
    "id": "9d2e4b8c1a7f53e06c4b9d2a8e1f0c57",
    "name": "Ted Annature",
    "email": "ted@annature.com.au",
    "mobile": "+61422000000",
    "mobile_otp": "+61422000000",
    "message": "Lorem ipsum dolor sit amet.",
    "message_sms": "Lorem ipsum dolor sit amet: {{token}}",
    "status": "sent",
    "account_id": "c64ce66b70b21c03bfd5dfa0ab14b730",
    "group_id": "a5a885caee6286a54ad7bbd4ab5400e9",
    "shared": false,
    "warning": null,
    "muted": false,
    "screening": false,
    "biometrics": false,
    "created": "2026-08-24T00:00:00Z",
    "cancelled": null,
    "completed": null,
    "purging": null,
    "purged": null,
    "metadata": {}
  }
  ```
</ResponseExample>