We’ve added a new field, national_identification_number, to the verification result for both Image Verification and Video Verification.

When a supported document contains a national identification number (for example, Italy’s Codice Fiscale on an ID Card or Tessera Sanitaria), it is returned in this field.

Learn more in our Image Identity Verification and Video Identity Verification guide.

You can now duplicate an existing Signature Request to create a new one based on the same configuration.

To do so, call the POST/signature_requests (see API reference) endpoint, and provide the signature_request_id of the Signature Request you want to duplicate.

The API creates a new Signature Request in draft status with a new id.

Learn more in the guide.

To help you better orchestrate you flows, we're adding the required_document_typefield in the response of Company Registry Verification.

This fields provides you the company document required to justify the existence of the company based on it's legal form and registries. Possible values are : company_certificate (KBIS), business_registration_certificate or rne_certificate.

Currently these values are only returned when verifying a French company ("country":"FR") and can be used to call our Document Analysis endpoint.

You can now access Audit Trails for six additional Verification types, providing a detailed record of what happened, when, and with what result throughout each Verification. Audit Trails are now available for the following Verifications:

• Video Identity Verification
• Watchlist Screening
• Proof of Address Verification
• Bank Account Document Check
• Bank Account Verification - Open Banking
• Bank Account Verification - SEPAmail

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)

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

When retrieving a Proof of Address Verification, the response now includes the document_type of the analyzed document.

This information will be returned when using the GET /verifications/proofs_of_address endpoint [see API reference]

For more details about Proof of Address verification, please refer to our guide.

You can now disable the sending of Decline to Sign emails by configuring the disabled_notifications parameter on a Custom Experience directly in our app or through the API. Add any of the following values to disable the corresponding email:

• signer.declined
• approver.declined
• sender.declined
• follower.declined

This works for both newly created and existing Custom Experiences.

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.

You can now retrieve the reason provided by an Approver when they reject a Signature Request directly from API responses.

This reason is available:

• In the responses of the Signature Request retrieval endpoints
• In the payload of the new signature_request.rejected Webhook event.

To learn more about Approvers, consult the Approver guide.

To help you create an even better and efficient integration with our API, a new Webhook event has been introduced: signature_request.automatic_reminder_executed. This event is fired whenever an automated reminder is sent to Signers or Approvers.

💡 This new event complements the existing manual reminder event signature_request.reminder_executed.

For Webhook setup details, see our Webhooks guide.

New behaviour for Webhook events subscription

Starting today, when you create or update a Webhook subscription, you can only subscribe to events that currently exist and not to events that may be added in the future.

Impact on new Webhook subscriptions

• In the application, the option “Trigger on all events (current and future)” is removed.
• In the API, the subscribed_eventsparameter of Webhook management endpoints still accepts the * value, but it now only covers the events that exist at the time of the creation or update. It will not include future events.

Impact on existing Webhook subscriptions

Existing Webhook subscriptions with subscribed_events set to * will continue to work, but they will only receive events that exist as of today.

Behavior when a new event is added to the API

When new Webhook events are added in the future, existing subscriptions with subscribed_events set to * will not receive them automatically. To receive newly added events, you will need to update your Webhook subscription to include them explicitly.

Why this change?

• When new events are introduced, automatically pushing them to all wildcard (*)-enabled Webhooks can generate noise, unexpected traffic, and unwanted side effects in your systems. By requiring explicit event selection, we ensure you only receive events you have chosen to handle.
• A more sober and intentional handling of events reduces unnecessary processing, simplifies troubleshooting while keeping the overall Webhook system efficient.

If you have any questions about this change, please contact our support team, we're here to help.

You can now duplicate a Template from the Sandbox environment to Production directly from the Yousign application.

This feature is particularly useful when you have created and tested a Template in Sandbox, and you want to use it for real in your Production environment, without creating it again manually.

From a Template in Sandbox, click “Duplicate to Production”, choose the destination Workspace, and the copy will be created automatically.

To learn more about Template management, please consult our dedicated guide.