Webhooks Overview
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 integration
Yousign 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 |
|---|---|
| signature_request.activated | This event is triggered whenever a Signature Request is activated. Signature Request status went from draft to ongoing. |
| signature_request.approved | This event is triggered whenever all Approvers have approved the Signature Request. Signature Request status went from approval to ongoing. |
| signature_request.canceled | This event is triggered whenever a Signature Request is manually canceled by a User. Signature Request status went from approval or ongoing to canceled. |
| signature_request.declined | This event is triggered whenever a Signer declines to sign the Signature Request. Signature Request status went from ongoing to declined. |
| signature_request.deleted | This event is triggered whenever a Signature Request is deleted (but still restorable). |
| signature_request.done | This event is triggered whenever a Signature Request is completed and all required Signers have signed. Signature Request status went from ongoing to done. |
| signature_request.expired | This event is triggered whenever a Signature Request reaches its expiration date without being completed. Signature Request status went from ongoing or approval to expired. |
| signature_request.permanently_deleted | This event is triggered whenever a Signature Request is permanently deleted. |
| signature_request.reactivated | This event is triggered whenever an expired Signature Request is manually reactivated. Signature Request status went from expired to ongoing or approval. |
| signature_request.reminder_executed | This event is triggered whenever a manual reminder is sent to Signers or Approvers. Signature Request status remains unchanged. |
Signer events
| Event | Description |
|---|---|
| signer.declined | This event is triggered whenever the Signer declines to sign the Signature Request. The reason provided by the signer is included in the webhook payload. |
| signer.done | This event is triggered whenever the Signer has signed. Signer status is signed. |
| signer.error | 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. |
| signer.identification_blocked | This event is triggered whenever the Signer failed to verify their identity, and cannot proceed further in the signature flow. This event is only triggered for the Advanced Electronic Signature (AES) level. |
| signer.identification_failed | 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. |
| signer.identification_succeeded | This event is triggered whenever the Signer succesfully verifies their identity, and can proceed further in the signature flow. This event is only triggered for the Advanced Electronic Signature (AES) level and Qualified Electronic Signature (QES) level. |
| signer.identity_saved | This event is triggered whenever the Signer saved their digital identity. If that Signer is invited to sign again, they will be able to reuse this identity for faster identification. This event is only triggered for the Qualified Electronic Signature (QES) level. |
| signer.link_opened | This event is triggered whenever the Signer has opened the signature link. |
| signer.notified | 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. Signer status went from initiated to notified. |
| signer.sender_contacted | This event is triggered whenever the Signer asked for a change in the Signature Request. This event is only available for the following electronic signature levels: Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES). |
Approver events
| Event | Description |
|---|---|
| approver.approved | This event is triggered whenever an Approver has approved a Signature Request. Approver status went from notified to approved. |
| approver.notified | This event is triggered whenever an Approver is ready to approve. This means a signature link has been sent to the Approver or can be retrieved, depending on the delivery mode. Approver status went from initiated to notified. |
| approver.rejected | This event is triggered whenever an Approver has rejected a Signature Request. Approver status went from notified to rejected.Signature Request status went from notified to rejected. |
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. |
Updated 1 day ago