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.

It is now possible to disable the email notification sent to Followers when a Signature Request is activated. This can be configured within the Custom Experience using the disabled.notifications parameter.

To disable this notification, specify the option follower.activated in the disabled.notifications parameter when using the following endpoints:

• Create a Custom Experience
• Update a Custom Experience

For more details, please refer to our dedicated guide.

We added two additional endpoints for adding or removing Labels from a Signature Request:

• Associate a Label with a Signature Request.
• Remove Label from a Signature Request.

More filters available:

• You can filter Signature Requests according to their Label name in the List Signature Requests endpoint. Filter format: label.name[eq]=<name>
• You can filter Labels according to their names in the List Labels endpoint. Filter format: name[eq]=<name>

For more details, please refer to the dedicated Label guide.

💡

What are Labels?

Labels are a categorization tag that can be attached to a Signature Request. They make it easier to organize, filter, and find Signature Requests both in your Yousign app and via the API.

It’s now possible to do the following with the API:

• Add Labels to a Signature Request
• Manage your organization’s Labels list (retrieve, create, update and delete Labels)

For more details, please refer to the dedicated Label guide.

Previously, when creating an ID document verification, the first_name and last_name parameters were required.

To allow flexibility to initiate a verification with or without names, the first_name and last_name are now optional for the endpoint POST /id_document_verifications.

For more details, please refer to the API reference.

The alignment parameter for Initials now supports vertical prefixes, allowing positioning relative to either the top or bottom of the page. This makes it easier to manage initials on documents with varying page sizes.

In the POST and PATCH document endpoints, the alignment parameter now supports the following values: top-left, top-center, top-right, bottom-left, bottom-center, and bottom-right.

For more details, see the Initials Guide.