You can now use Document Analysis inside Workflows, simply by passing the optional parameter : workflow_session_id in the Initiate Document Analysis endpoint .

The results of the Document Analysis will be visible in your Workflows Dashboard and you can choose to resolve manually a Document Analysis by calling the : Resolve an Action endpoint and passing the corresponding ressource type (ie : driver_licence_document_analysis).

You can now disable three Approver notification emails directly from a Custom Experience.
Add the following values to the disabled_notifications list to suppress these emails sent by Yousign when delivery_mode is email: approver.notified, approver.approvedand approver.rejected.

This works for both newly created Custom Experiences and those you already have in place.

Configure this via the Custom Experience creation endpoint POST /custom_experiences or by updating an existing Custom Experience PATCH /custom_experiences.
Learn more about configuring Custom Experiences in our guide and how email delivery works in Delivery mode.

You can now access Audit Trails for your Verifications, providing a detailed record of what happened, when, and with what result.

Audit Trails are currently available for Image Identity Verification and Company Registry Verifications, with support for other Verification types coming soon.

Each supported Verification includes its own PDF Audit Trail, available via:

• the Yousign app, from the Workflow dashboard (learn more about Workflows), or
• the API endpoint GET /verifications/{verificationType}/{verificationId}/audit_trail (see API reference)

These Audit Trails serve as proof of the Verification process. Each includes a JSON record that is securely archived using a trusted evidential process to guarantee its integrity, along with a readable PDF version available for download.

Learn more in our dedicated guide section.

You can now retry an Action in a Workflow Session when its status is blocked, until it reaches a done status.

This update gives you more control and better visibility when handling repeated Action attempts — particularly useful when managing sessions from your in-app dashboard.

Learn more about how retries work in this section of our guide.

Effective immediately, SMS OTP cannot be delivered to phone numbers in China due to newly tightened local restrictions on inbound SMS traffic. As a result, Signers with Chinese phone numbers cannot use SMS OTP for authentication.

If you currently set the signature_authentication_mode to opt_sms in the Signer creation endpoint, authentication by SMS will not be possible for Chinese numbers. Please use one of the following alternatives:

• Use Email one-time password by setting signature_authentication_mode to opt_email.
• If you are using Advanced Electronic Signature (AES), consider upgrading to Qualified Electronic Signature (QES) for Chinese Signers, which does not rely on SMS OTP.

For more details, see our Authentication modes guide.

You can now use our Document Analysis endpoint to extract and check data on two new document types :

• French new format driver licences (⚠️ we currently not handle old driver licenses formats)
• RNE certificates also know as : Attestation d'immatriculation au registre national des entreprises

To request a new Document Analysis for a driver_licence or rne_certificate document simply specify :

• "type" : "driver_licence"
• or "type" : "rne_certificate"

To check whether a person appears on the document, you can optionally add :

• checks[first_name]
• checks[last_name]

Additionally we will return a dedicated status_code : DA_1002 when the driver's licence is expired or when the RNE certificate is older then 3 months.

You can now use our Document Analysis endpoint to extract and check data for a Business Registration Certificate. For now we only support the French Document called : Avis de situation.

To request a new Document Analysis for a business_registration_certificate document simply specify :

• "type" : "company_certificate"

To check whether a person appears in the legal representatives extracted from the KBIS, you can optionally add :

• checks[legal_representatives][0][first_name]
• checks[legal_representatives][0][last_name]

In addition to those checks, we also use the issuance_date of the document to check whether the document is older then 3 months.

We improved our Consumption endpoints to include verifications add-ons, enabling you to track the consumption of all verification products.

• GET /consumptions/addons(see API reference)

This endpoint now returns all purchased verification add-ons for the current subscription period, including their consumed quantity since the start of the period.

You can also filter results using 9 new add-on values, covering all verification services.

• GET /consumptions/detail(see API reference)

This endpoint returns the aggregated Consumption of your verification products over a given period.

To help distinguish between different verification services, the response now includes a new field: verification_type, allowing you to identify which verification generated each Consumption entry.

For more information on consumption, you can consult our dedicated guide.

Previous validation rules for the first_name, last_name and legal person nameparameters could lead to situations where the verification remained stuck in a pending status.

To address this, we’ve introduced new validation rules for the following endpoints:

• [POST /verifications/identity_documents] (see API reference)

• [POST /verifications/bank_accounts] (see API reference)

• [POST /verifications/proofs_of_address] (see API reference)

Updated validation rules

• first_name and last_name:

^[('|’)]?[\d\p{L}\p{M}+][-\d\p{L}\p{M}+.'’ ]*$

• legal_person name(only for the POST /verifications/bank_accounts) : maximum length of 128 characters

Impact of this change

Any verification request not complying with the new rules will now return a 400 Bad Request error.

We recommend reviewing your current integration to ensure compliance with the updated validation rules.

We have added three endpoints to retrieve your Consumption records in JSON. These complement the existing aggregated Consumption endpoint and expose the same level of detail currently available in the app’s CSV export, so you can see exactly for which Signature Request, Signer, or Document services were consumed, and when.

• GET /consumptions/records/invited_signers (see API reference)
• GET /consumptions/records/identifications (see API reference )
• GET /consumptions/records/electronic_seals (see API reference)

Availability: Production only (no consumption is recorded in Sandbox).