# QES verification ready

This webhook is triggered when a QES signer's verification session is created and they can verify their identity. It is sent once for each QES signer, in signing order, while the envelope is qes_in_progress. It is not sent again if an existing session is reused. See the QES guide for the full flow.

Endpoint: POST qes-ready
Version: 1.0.0
Security: basicAuth

## Request fields (application/x-www-form-urlencoded):

  - `envelope_fingerprint` (string, required)
    A string representing the envelope
    Example: "584ea8b41b0d4c17a96b967433b211e6"

  - `envelope_meta` (string)
    A JSON string of any meta information added to the envelope

  - `party_id` (integer, required)
    ID of the party who can now verify
    Example: 45631119

  - `contact_id` (integer, required)
    ID of the contact linked to the party
    Example: 7418454

  - `contact_name` (string, required)
    Name of the signer
    Example: "Abby"

  - `contact_email` (string, required)
    Email address of the signer
    Example: "abby@signable.co.uk"

  - `signing_page_link` (string,null, required)
    Link the party opens to verify their identity. Only set when embedded signing is enabled for your company, otherwise null.
    Example: "https://sign.signable.app/#..."

  - `verification_session_expires_at` (string, required)
    UTC timestamp of when the party's verification session expires
    Example: "2026-11-09T14:37:47+00:00"

  - `company_id` (integer, required)
    ID of the company the envelope belongs to
    Example: 64034

  - `action` (string, required)
    The action taken. Defaults to qes-ready.
    Example: "qes-ready"

  - `action_date` (string, required)
    UTC timestamp of when the session was created
    Example: "2026-10-26T14:37:47+00:00"


## Response 200 fields
