✨ We have reorganized our Guides section to make it easier for you to find the information you need. The structure now features new categories for improved navigation and clarity.
In addition, we’ve reworked the following introduction pages to provide clearer and more detailed content:

• Introduction
• Set up your account
• Postman collection
• Stay updated with our Changelog
• Electronic Signature
• Hot to guide - Create your first Signature Request

This is just the beginning! We are committed to continuously improving our Guides, so stay tuned for further updates.

It's now possible to set or update a Document name when uploading or modifying a Document linked to a Signature Request:

• Document upload: A new optional parameter name is available in the endpoint POST /signature_requests/{signatureRequestId}/documents (see API reference).
• Document update: You can also rename an already uploaded Document using the name parameter in the endpoint PATCH /signature_requests/{signatureRequestId}/documents/{documentId} (see API reference).

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

You can now prevent signers from downloading documents before signing by using the download_documents_disabled parameter in Custom Experiences.

This parameter is available in:

• The Custom Experience creation and update endpoints.
• The Custom Experience creation and update flows in the app. Learn more in our Help Center.

More details on creating Custom Experiences can be found in our guide section.

You can now require signers to manually copy a predefined text during the signing process, with Yousign automatically verifying the input. This ensures that the text matches your requirements without the need for manual review after signature.

This feature is available through the existing POST /consent_requests endpoint, which now supports a new type, text_to_copy.

For more details on how to configure the Text to copy feature, please visit our Guide.

When a Signature Request is created from the app with associated Labels, these Labels are now included in the response payload of relevant Signature Request endpoints, such as List Signature Requests.

Learn more about labels in this article.

This feature allows to automatically organize Signature Requests created from the app via API based on their labels.

For now, it is only possible to read labels via API. The ability to add labels to Signature Requests via API is not yet available, but we are currently working on this improvement.

This feature enables approvers and signers in a Signature Request to view a list of recipients and track their activity progress.

You can configure this setting in Custom Experiences using the parameter recipients_activity_disabled (default: true) in the following endpoints:
POST - Create a Custom Experience
PATCH - Update a Custom Experience

For additional details, please refer to our documentation.

The maximum length for the custom content added to notification and reminder emails has been increased from 500 to 2000 characters.

You can customize the email body using the following parameters:

• email_notification.custom_note in the Signature Request creation or update endpoint.
• custom_text.request_body and request_body.reminder_body in the Signer creation or update endpoint.

Those changes are also available for Signature Requests created on our web application.

More details on customizing email content can be found in our guide section.

It is now possible to disable specific email notifications for each Signer of the Signature Request when the delivery mode email is used.

All you have to do is to specify for each signer, which email should not be sent, using the email_notification.disabled parameter.

To learn more about this feature, feel free to read our documentation or consult the API reference.

The timezone parameter of the POST /signature_requests endpoint is used to:

• Define the time zone displayed in emails.
• Calculate the expiration date of the Signature Request.

NEW - It now also defines the date and time displayed in the PDF Audit Trail.

You can now strengthen identity verification through video by adding a face recognition step. This new feature provides an extra layer of security by comparing the user’s face on the video to the photo extracted from on their ID document.

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

📘

Beta feature

The Video 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.