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.

It is now possible to link a document to a Signer Consent Request by specifying a documentId when creating the Signer Consent Request. This enables the addition of a text link after documents verification at the Consents validation step in the signing flow, allowing Signers to open the document in a modal and identify which document the consent applies to.

The documentId will not be displayed in the audit trail, as the Signer Consent Request remains attached to the Signature Request.

How to Contextualise a Signer Consent Request:

1. Upload the document – Retrieve the documentId after uploading a document via POST /signature_requests/{signatureRequestId}/documents (see API reference)
2. Create a Signer – A Signer must be created before adding a Signer Consent Request via POST /signature_requests/{signatureRequestId}/signers (see API reference)
3. Create a Signer Consent Request – Specify the documentId when creating the Signer Consent Request via POST /signature_requests/{signatureRequestId}/consent_requests (see API reference)

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

Three new types of Signer's Fields are now supported for signatures completed through your custom-built signing flow—that is, without using Yousign's pre-made signature interface.

The new supported fields are:

• Text Fields: to collect structured input from a Signer.
• Radio Groups: to let a Signer select one option of a limited number of choices.
• Checkboxes: to let a Signer choose one or more options of a limited number of choices.

For setup instructions and more details, consult our guide on building your own signing flow.