You can now control the order in which multiple Approvers validate a Signature Request by setting the parameter ordered_approvers to true in the Signature Request creation endpoint.

When enabled:

• Approvers will be notified and required to approve one after the other.
• The order is based on how Approvers are added. You can override it using the insert_after_id parameter when creating or updating an Approver.

For more details, refer to this guide.

Introducing Company Verification from a company identification file

You can now request a Company Verification by uploading a company identification file using the dedicatedInitiate a Company Verification endpoint using the file and country_code parameters in multipart format.

We currently only support : French Company Identification Documents (KBIS). See our full guide here.

New responses on the Retrieve a Company Verification Details endpoint and verification.company.done Webhook.

To reflect this change the response payloads have been updated to include a new node containing the extracted data from the document

New company verification status.

To clearly indicate a failure in the extraction, we are introducing a new company verification status called inconclusive . Inconclusive company verifications are not billed. More details can be found in our documentation here.

The following limits now apply on Sandbox during the API trial period:

• Maximum recipients per Signature Request:
  • 5 Signers
  • 5 Approvers
  • 5 Followers
• Daily sending limit:
  • 100 Signature Requests

For more details, see the Limits guide.

The signer.identification_succeeded and signer.identification_failed events are now triggered for the Advanced Electronic Signature (AES) Level.

Check the API reference for more details :

• signer.identification_failed (link to API reference)
• signer.identification_succeeded (link to API reference)

Using Advanced Electronic Signature (AES) always required users to upload an identity document before signing.

As a result, integrating Yousign in user flows that already required an identity verification step was creating friction since Signers were asked to upload their identity documents twice.

Pre-Identity Verification for AES, aims to provide a simpler way to integrate Yousign in complex flows by allowing you to verify an identity before giving signers access to the signing flow, all while maintaining Yousign’s secured and certified AES. This way, signers have to upload their identity documents only once in your entire business flow.

What's new?

A new signer parameter

You can now use the pre_identity_verification_required parameter when creating a Signer via the Signer creation endpoint or when updating a Signer to indicate that a signer will go through a pre-verification process.

A new endpoint to pre-verify an identity

Use the new endpoint (see API reference)

POST /signature_requests/{signatureRequestId}/signers/{signerId}/identity_verification

to submit and verify an identity document before the signature process.

---

📘 To learn how to implement this in your flows, the conditions for using it, and how the signing flow changes when using pre-verification, check out our full guide :

• Pre-identity verification guide for AES (link to guide).

To deliver a more consistent and seamless developer experience, we’ve redesigned the company verification service, enhancing its scalability, robustness, and future readiness.

Here’s what changed:

Updated response structure on creation endpoint

The company verification creation endpoint now only returns a minimal response, indicating that the verification is in progress with a new pending status.

Since the final verification results are no longer included in this response, you will be able to access them through the following:

• A new Webhook event
  We introduced a Webhook to notify you when a company verification has been processed.
• A new endpoint to retrieve company verification results
  You can now retrieve a company’s verification detailed data using the new GET endpoint. Simply use the id returned from the verification creation.

For more details on how to integrate the company verification flow, please refer to our dedicated guide.

You can now fully customize email content at both the Signature Request level and the individual recipient level: Signers (already existing) and Approvers (new).

Four fields are available for customization:

• Subject and custom message for the invitation email
• Subject and custom message for the reminder emails

For full details, see our updated Email Customization Guide.

Following the release of the Seal&Sign feature, it is now possible to sign a document and then easily apply an Electronic Seal to it.

You can now use a previously signed Document as a parameter when calling the POST /electronic_seal_documents endpoint (see API reference) to create a sealed version of the Document. (see How to create an electronic Seal for details about Sealed Document).

Simply provide the signature_request_document_id in the request payload. This operation will generate a new copy of the signed Document with the Seal applied, allowing you to preserve both the original and the sealed versions.

For more details on how to apply a Seal to a signed Document, please refer to our dedicated guide.

You can now explore all Yousign webhook event payloads directly in the API reference section of our documentation!

✅ What’s new:

• Each webhook event is fully documented in our OpenAPI Specification.
• You can now see the exact payload structure for each event type.
• The documentation is now more exhaustive, structured, and easier to browse.

This update makes it much simpler to understand how to handle webhook data in your integration.

👉 Head over to the API reference and check out the “Webhook Events” section!

To simplify the experience across all our verification products, we’ve redesigned several aspects of the solution for:

• Video identity verification
• Document identity verification
• Bank account verification

This redesign includes renamed endpoints and parameters, richer response payloads, new statuses and status codes, and updated Webhook events.

What is changing?

Endpoint route naming

We've updated the naming of several endpoints to group them under a more consistent namespace:

Endpoint parameter names

Some parameter names have been harmonized across verification types:

Response format changes

We’ve enriched all the POST and GET endpoints by providing more information in the responses.

For example, before, only the id was returned when initiating a verification.

Now you’ll also receive:

• workspace_id
• created_at, updated_at
• status
• status_codes
• data_anonymized
• data

This gives you better visibility into the lifecycle of a verification.

New status & status codes

• New status

We’re aligning the former approved and declined statuses across all verification types:

• New status codes

New prefixed status codes help identify the type of verification:

Webhook

Event names have been updated for clarity and alignment:

The Webhook payloads have also been improved for better traceability.

📘 For full details on all changes, including routes, parameters, payload examples, check out our updated guides:

• Video identity verification guide
• Document identity verification guide
• Bank account verification guide