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

  1. 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)
  2. When an event happens, Yousign sends an HTTP POST request to your endpoint.
  3. 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

EventDescription
signature_request.activatedThis event is triggered whenever a Signature Request is activated.
Signature Request status went from draft to ongoing.
signature_request.approvedThis event is triggered whenever all Approvers have approved the Signature Request.
Signature Request status went from approval to ongoing.
signature_request.canceledThis 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.declinedThis event is triggered whenever a Signer declines to sign the Signature Request.
Signature Request status went from ongoing to declined.
signature_request.deletedThis event is triggered whenever a Signature Request is deleted (but still restorable).
signature_request.doneThis 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.expiredThis 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_deletedThis event is triggered whenever a Signature Request is permanently deleted.
signature_request.reactivatedThis event is triggered whenever an expired Signature Request is manually reactivated.
Signature Request status went from expired to ongoing or approval.
signature_request.reminder_executedThis event is triggered whenever a manual reminder is sent to Signers or Approvers.
Signature Request status remains unchanged.

Signer events

EventDescription
signer.declinedThis 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.doneThis event is triggered whenever the Signer has signed. Signer status is signed.
signer.errorThis 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_blockedThis 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_failedThis event is triggered whenever the Signer failed to verify their identity. This event is only triggered for the Qualified Electronic Signature (QES) level. The reason for failure is included in the webhook payload.
signer.identity_savedThis 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_openedThis event is triggered whenever the Signer has opened the signature link.
signer.notifiedThis 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_contactedThis 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

EventDescription
approver.approvedThis event is triggered whenever an Approver has approved a Signature Request.
Approver status went from notified to approved.
approver.notifiedThis 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.rejectedThis 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

EventDescription
contact.createdThis event is triggered whenever a Contact is created.

Document Verification events

EventDescription
verification.bank_account.doneA bank account details verification has been processed.
verification.identity_document.doneAn identity document verification has been processed.
verification.identity_video.doneA video identity verification has been processed.

Electronic Seal events

EventDescription
electronic_seal.doneElectronic Seal processed successfully.
electronic_seal.errorElectronic Seal processing failed.

User events

EventDescription
user.completedThis event is triggered whenever a User completed their invitation. User status is completed.