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:

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.

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.

✨ 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:

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.