You can now track each signer's QES verification while an envelope is `qes_in_progress`, and use QES with embedded signing.

## New webhooks

- `qes-ready`: a QES signer can now verify. The full payload includes the signer's `signing_page_link` (embedded signing only) and `verification_session_expires_at`.
- `qes-signed`: a QES signer has verified and their qualified signature has been applied.
- `qes-failed`: QES signing failed. The envelope status changes to `failed`.


For each QES signer, `qes-ready` is sent first, then `qes-signed`. After the last QES signer, `signed-envelope-complete` is sent.

## New party fields

[`GET /envelopes/{envelope_fingerprint}`](/openapi/envelopes/getenvelope) now returns these fields for each party:

- `party_qes_status`: `waiting`, `ready`, `complete` or `failed`.
- `party_qes_session_expires_at`: when the party's verification session expires.
- `party_signing_url`: the party's signing page link, when embedded signing is enabled for your company.


## QES with embedded signing

QES is now available to companies using embedded signing. If you have turned off **Signer notification emails**, Signable does not send QES signers the ID verification email. Send each signer their link when you receive `qes-ready`.

See [Using QES with the API](/guides/qes) for details.