# Verify proof (optional)

Optional endpoint to verify a proof hash from a previous successful validation.
This can be used to confirm that a validation was completed successfully.

Endpoint: PATCH /v1/validations/{token}
Version: 1.0.0
Security: ApiKeyAuth

## Path parameters:

  - `token` (string, required)
    The validation token returned from the start validation endpoint
    Example: "val_7af7215261b8497cb355e617b13f4ef2"

## Request fields (application/json):

  - `proof` (string, required)
    The proof hash to verify
    Example: "86dd8444ed76402c93ce62497cb29a0d7af7215261b8497cb355e617b13f4ef2"

## Response 200 fields (application/json):

  - `valid` (boolean)
    Whether the proof is valid

  - `phoneNumber` (string)
    The validated phone number

  - `verifiedAt` (string)
    When the validation was completed

## Response 400 fields (application/json):

  - `message` (string, required)
    Human-readable error message
    Example: "Invalid code"

  - `error` (string)
    Error code for programmatic handling
    Example: "INVALID_CODE"

  - `attemptsRemaining` (integer)
    Number of verification attempts remaining (only for verification errors)
    Example: 3

## Response 401 fields (application/json):

  - `message` (string, required)
    Human-readable error message
    Example: "Invalid code"

  - `error` (string)
    Error code for programmatic handling
    Example: "INVALID_CODE"

  - `attemptsRemaining` (integer)
    Number of verification attempts remaining (only for verification errors)
    Example: 3

## Response 500 fields (application/json):

  - `message` (string, required)
    Human-readable error message
    Example: "Invalid code"

  - `error` (string)
    Error code for programmatic handling
    Example: "INVALID_CODE"

  - `attemptsRemaining` (integer)
    Number of verification attempts remaining (only for verification errors)
    Example: 3


## Response 404 fields