Webhooks
This page introduces how Yousign webhooks work, what events you can subscribe to across our products, and why they’re essential for building real-time integrations.
Webhooks allow your application to automatically receive notifications about key events happening across Yousign’s products. Instead of polling our API to check whether something has changed, you can subscribe to specific events and receive real-time HTTP notifications when they happen.

Why Use Webhooks?
Yousign webhooks are the recommended way to stay in sync with what’s happening in your workflows. They’re fast, efficient, and ideal for automation.
Key benefits:
- Real-time notifications – Be instantly informed when a document is signed, an identity is verified, or a seal is applied.
- No polling required – Avoid hitting API rate limits by reacting to events instead of checking for updates.
- Designed for automation – Use webhooks to trigger actions in your system like sending notifications, updating records, or downloading signed documents.
Webhooks are available for all Yousign products:
- ✅ eSignature: Events related to Signature Requests, Signers, and Approvers
- ✅ eSeal: Events for processing seals on documents
- ✅ Document Verification: Events for ID video checks, document analysis, and more
Zapier integrationYousign webhook subscriptions can also be connected to Zapier, either using our off-the-shelf integration or by configuring your own webhook trigger.
How it works
- Create a webhook subscription and define:
- Which events you want to listen to
- Which environment you’re working in (sandbox or production)
- Where to send the notifications (your endpoint)
- When an event happens, Yousign sends an HTTP POST request to your endpoint.
- Your app handles the request and uses the data to react in real-time.
Want to start right away? → Learn how to create a subscription
🔔 Available events
Below is a categorized list of all webhook events supported.
Each event includes a short description and a link to its full payload in our API Reference.
Signature Request events
Event | Description |
---|---|
This event is triggered whenever a Signature Request is activated. | |
This event is triggered whenever all Approvers have approved the Signature Request. | |
This event is triggered whenever a Signature Request is manually canceled by a User. | |
This event is triggered whenever a Signer declines to sign the Signature Request. | |
This event is triggered whenever a Signature Request is deleted (but still restorable). | |
This event is triggered whenever a Signature Request is completed and all required Signers have signed. | |
This event is triggered whenever a Signature Request reaches its expiration date without being completed. | |
This event is triggered whenever a Signature Request is permanently deleted. | |
This event is triggered whenever an expired Signature Request is manually reactivated. | |
This event is triggered whenever a manual reminder is sent to Signers or Approvers. |
Signer events
Event | Description |
---|---|
This event is triggered whenever the Signer declines to sign the Signature Request. | |
This event is triggered whenever the Signer has signed. Signer status is | |
This event is triggered whenever the Signer failed to sign due to an internal error during the signing process. In that case the Signature Request is automatically cancelled. | |
This event is triggered whenever the Signer failed to verify their identity, and cannot proceed further in the signature flow. | |
This event is triggered whenever the Signer failed to verify their identity. This event is only triggered for the Qualified Electronic Signature (QES) level and The Advanced Electronic Signature (AES). The reason for failure is included in the webhook payload. | |
This event is triggered whenever the Signer succesfully verifies their identity, and can proceed further in the signature flow. | |
This event is triggered whenever the Signer saved their digital identity. | |
This event is triggered whenever the Signer has opened the signature link. | |
This event is triggered whenever the Signer is ready to sign. This means a signature link has been sent to the Signer or can be retrieved, depending on the delivery mode. | |
This event is triggered whenever the Signer asked for a change in the Signature Request. | |
This event is triggered when the first notification email sent to a Signer fails to be delivered due to a delivery error (e.g., invalid email address, soft bounce, spam block). |
Approver events
Event | Description |
---|---|
This event is triggered whenever an Approver has approved a Signature Request. | |
This event is triggered whenever an Approver is ready to approve. | |
This event is triggered whenever an Approver has rejected a Signature Request. | |
This event is triggered when the first notification email sent to an Approver fails to be delivered due to a delivery error (e.g., invalid email address, soft bounce, spam block). |
Contact events
Event | Description |
---|---|
contact.created | This event is triggered whenever a Contact is created. |
Document Verification events
Event | Description |
---|---|
verification.bank_account.done | A bank account details verification has been processed. |
verification.identity_document.done | An identity document verification has been processed. |
verification.identity_video.done | A video identity verification has been processed. |
verification.company.done | A company verification has been processed. |
Electronic Seal events
Event | Description |
---|---|
electronic_seal.done | Electronic Seal processed successfully. |
electronic_seal.error | Electronic Seal processing failed. |
User events
Event | Description |
---|---|
user.completed | This event is triggered whenever a User completed their invitation. User status is completed . |
Workflow events
Event | Description |
---|---|
workflow_action_group.started | This event is triggered when an Action Group in a Workflow Session reaches the ongoing status. |
workflow_action_group.blocked | This event is triggered when an Action Group in a Workflow Session reaches the blocked status. |
workflow_action_group.done | This event is triggered when an Action Group in a Workflow Session reaches the done status. |
workflow_session.started | This event is triggered when a Workflow Session reaches the ongoing status. |
workflow_session.blocked | This event is triggered when a Workflow Session reaches the blocked status. |
workflow_session.done | This event is triggered when a Workflow Session reaches the done status. |
Updated 2 days ago