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.

To ensure the highest levels of security and reliability, we are updating our infrastructure by removing outdated protocols that no longer meet modern standards.

This upgrade reflects our commitment to staying at the forefront of industry best practices, protecting your data, and delivering state-of-the-art services.

What is changing?

To maintain a high level of security, we will remove the support of security protocol TLS 1.1 from our infrastructure. This means that older and less secure cipher suites will no longer be supported.

Cipher suites are groups of algorithms that secure network connections. Their strength is critical for ensuring your data remains private, intact, and authentic while traveling online.

By deprecating weak cipher suites, we are enhancing our security, improving performance, and ensuring compliance with modern industry standards.

How are you impacted?

🚧

Starting April 16, 2025, these outdated components will be disabled. Any connections using weak cipher suites will be refused.

To avoid any disruption, it is essential that you ensure your systems and applications are compatible with modern cipher suites.

What action do you need to take?

To help you get prepared, we’ve set up a test environment so you can verify your compatibility.

You can access this environment from this URL: https://ciphers-test.yousign.app

For API Users:

• Identify your integration team or provider and ask them to verify your compatibility with modern cipher suites.
• Ask them to reach our test URL from your integration and confirm that it returns a valid response.

For APP Users:

Ensure you are using a modern operating system and up-to-date browser and open the test URL mentioned above to check compatibility.

• If you can successfully reach the page, your system is compatible, and no actions are needed.
• If you cannot access the page, this means your system uses old components and should be updated. We kindly recommend checking with your IT team to ensure your system is using the latest versions for optimal security.

How can you get additional assistance?

If you need further guidance or assistance, feel free to visit our Help Center.

Thank you for your attention to this important update. Ensuring the security of your data is our top priority, and we appreciate your cooperation as we make these enhancements.

Following the release of the Signer Consent Request, this feature is now also supported for Qualified Electronic Signatures (QES). You can request Signer Consent via checkbox or copied text, and the consent decision will be recorded in the Signature Request audit trail after signing.

For more details on how to use the Signer Consent Request, check out our dedicated guide.

You can now test the Document and Identity Verification solution directly in Sandbox. Simulate any type of verification, whether successful or failed, to fit your testing scenarios.

For more details about this service, refer to our Document and Identity Verification guide.

📘

Beta feature

The Document and Identity Verification feature is currently in Beta and available to a limited number of clients. If you are interested in accessing this new product, you can join the waiting list.

For each verification type (Video Identity Verification, Identity Document Verification or Bank Account Verification), you can now list all the verification requests. For each verification, you will get the following details: the ID, the creation and last update dates, the current status and the associated error codes if any.

For more details about this service, refer to our Document and Identity Verification guide.

📘

Beta feature

The Document and Identity Verification feature is currently in Beta and available to a limited number of clients. If you are interested in accessing this new product, you can join the waiting list.