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.

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.

Only DOCX and PDF were previously supported as attachment formats in a Signature Request. To enhance flexibility, you can now upload PNG, JPEG, and JPG files as attachments.

Please note:

• These formats are for attachments only and cannot be signed.
• This feature is only available via API.

When uploading PNG, JPEG, or JPG files, you must specify the nature parameter to attachment in the following endpoints:

• Upload a document file (POST /signature_requests/{id}/documents/upload)
• Update a document (PATCH /signature_requests/{id}/documents/{document_id})

For more details, please refer to the guide section.

Three new types of 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:

• Mentions: add legal or informational mentions.
• Initials: allow signers to add their initials at specific locations on the document.
• Read-only text fields: display non-editable text within the document.

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

Following the release of the feature allowing you to set or update a Document name when uploading or replacing a Document associated with a Signature Request, we have now updated it to support additional characters.

The name parameter must match the following naming pattern:/^(?!\s)[^\/\\]+(?<!\s)$/:

• Names cannot start or end with a space.
• Names can contain any character except / or \.

These rules help ensure consistent and valid Document names. For more details, please consult our guide on managing Documents.

A new locale ptis available for your audit trails in Portuguese.

You can now choose between en, fr, es, de,it or pt.

By default, en will be used (current behavior).

This option can be set when initiating a Signature Request with audit_trail_locale field.

You can now choose how your Custom Experience logo is displayed using the logo_layout parameter in the Create a Custom Experience and Update a Custom Experience endpoints.

Two layout modes are available:

• round: the logo will be framed inside a circle (default layout).
• original: the logo will be displayed in its original shape and ratio.

For more details on how to use the logo_layout parameter, check out our dedicated guide section.