You can now explore all Yousign webhook event payloads directly in the API reference section of our documentation!

✅ What’s new:

• Each webhook event is fully documented in our OpenAPI Specification.
• You can now see the exact payload structure for each event type.
• The documentation is now more exhaustive, structured, and easier to browse.

This update makes it much simpler to understand how to handle webhook data in your integration.

👉 Head over to the API reference and check out the “Webhook Events” section!

To simplify the experience across all our verification products, we’ve redesigned several aspects of the solution for:

• Video identity verification
• Document identity verification
• Bank account verification

This redesign includes renamed endpoints and parameters, richer response payloads, new statuses and status codes, and updated Webhook events.

What is changing?

Endpoint route naming

We've updated the naming of several endpoints to group them under a more consistent namespace:

Endpoint parameter names

Some parameter names have been harmonized across verification types:

Response format changes

We’ve enriched all the POST and GET endpoints by providing more information in the responses.

For example, before, only the id was returned when initiating a verification.

Now you’ll also receive:

• workspace_id
• created_at, updated_at
• status
• status_codes
• data_anonymized
• data

This gives you better visibility into the lifecycle of a verification.

New status & status codes

• New status

We’re aligning the former approved and declined statuses across all verification types:

• New status codes

New prefixed status codes help identify the type of verification:

Webhook

Event names have been updated for clarity and alignment:

The Webhook payloads have also been improved for better traceability.

📘 For full details on all changes, including routes, parameters, payload examples, check out our updated guides:

• Video identity verification guide
• Document identity verification guide
• Bank account verification guide

We have added three new properties to text, checkbox, and radiogroup Fields:

• name: Set a readable name to help identify and manage Fields. This won’t be visible to recipients.
• default_value: Pre-fill Fields with known information.
• read_only: Lock pre-filled Fields to prevent edits by Signers.

For more details, please refer to the API Reference.

The Qualified Electronic Seal is now available through the Yousign API!
It allows companies (legal persons) to seal documents without requiring the actions linked to a signature process.
It prevent the risk of fraud and proves document authenticity and integrity.
In addition to simpler use cases, we advise using this seal level in particular for electronic invoicing and notary deeds.

Please reach out to your customer representative to activate this product on your account.

Guide
https://developers.yousign.com/docs/qualified-electronic-seal

Endpoint
https://developers.yousign.com/reference/post-electronic-seals

We've enhanced Text to Copy Consent by providing real-time error highlighting. When the Signer makes a mistake, the incorrect character will be highlighted in red. Once correct, the text will turn green, making it easier to identify and fix errors.

Additionally, input is now restricted to the exact number of characters specified in the instruction, helping Signers avoid mistakes and enter the text accurately.

For more details about this feature, please refer to our guide.

You can now request a Company Verification by providing a company identification number.

For more details about this service, please refer to our Company Verification guide.

You can now manage how your Signature Requests are embedded in your applications or websites directly from the Yousign interface. A new iFraming settings page is available in your Application, under API > iFraming.

From there, you can:

• Choose between three security modes (not authorized, authorized domains only, origin referer always authorized)
• Add and manage authorized domains for embedding Signature Requests

💡

Any previous settings configured with our Support Team remain unchanged and continue to apply.

For more details, refer to our guide.

We have improved how identification errors are displayed to Signers during the Qualified Electronic Signature (QES) process. Error messages are now clearer, better structured, and include explicit guidance on how to resolve issues and successfully complete the next attempt.

Here are the possible identification errors a Signer may encounter if the procedure fails.

Previously, only one first name from a Signer’s list of given names was accepted for identity validation during the Qualified Electronic Signature (QES) flow. For example, if a Signer’s ID document lists "Eve Louise Coralie", only one of these names —"Eve", "Louise", or "Coralie" — needs to be used.

Starting today, we now accept any combination of all given names as a valid first name for a Signer! This means "Eve Louise Coralie" can now be used as a valid first name for the identification phase in the QES flow.

For more details, please refer to our dedicated API guide.

We have expanded the supported characters for Signers firstName and lastName by adding the following ones: Ș, ș, Ț, ț. These changes have been applied for all Signature Levels.