We are reaching out to inform you of an infrastructure update that may require action from your IT team to ensure uninterrupted access to Yousign services.

📅 Effective date: April 30, 2026

What is changing?

As part of ongoing improvements to the resilience and scalability of our infrastructure, Yousign will be introducing new IP address ranges.

⚠️ Action required

Please update your network security configuration (Firewall / Allowlist) to authorize the new IP addresses before April 30, 2026.

1. New IP addresses to ADD:

• 57.130.41.144/28 (range 57.130.41.144 → 57.130.41.159)
• 51.38.96.112/28 (range 51.38.96.112 → 51.38.96.127)

2. Existing IP addresses to KEEP:

• 5.39.7.128/28 (range 5.39.7.128 → 5.39.7.143)
• 52.143.162.31
• 51.103.81.166

Does this affect you?

This update applies to your organization if you enforce strict network security policies, including:

• Inbound traffic (Webhooks): Your servers only accept requests from known IP addresses when using Yousign's webhook APIs.
• Outbound traffic (Corporate firewall): Your internal network restricts outgoing connections to specific IP addresses rather than domains.

💡 Does this email seem too technical? We recommend forwarding it to your IT team responsible for the Yousign integration. They will know what steps to take.

What happens if no action is taken?

If your configuration is not updated before April 30, communications with Yousign may be blocked. This could result in an inability to receive webhook notifications or to connect to our API/Application.

Environments affected:

• Production: https://yousign.app & https://api.yousign.app
• Sandbox: https://api-sandbox.yousign.app

You have time, and we are here to help

We wanted to give you plenty of advance notice so you can carry out this update at your own pace, in coordination with your technical teams if needed.

Our team is fully available to answer any questions or to support you through this transition.

You can now generate dedicated links to collect and verify Documents for your end users.

Workflows Session Links allow you to verify documents without having to develop the entire interface or business logic on you side.

How it works:

• Our team sets up a Workflow Template based on your use case.
• You create a Workflow Session for each customer journey using the template.
• You create an Applicant. This represents the end user you are verifying.
• You Attach Verifications to that Applicant, based on your Workflow Template.
• You retrieve the Workflow Session Link and share it to your end user.

You can the easily follow the results of the Workflow Session, via dedicated Webhooks or directly in you Workflow Dashboard.

Learn more in our dedicated guide.

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

• French and Italian vehicle registration certificates (Carte grise and Libretto auto respectively).
• French auto insurance claims history documents (commonly called Relevé d'informations).
• Italian temporary vehicle registration certificates (commonly called : Permesso di circolazione).

To request a new Document Analysis for these new types use :

• "type" : "vehicle_registration_certificate" / " temporary_vehicle_registration_document" / auto_insurance_claims_history"
• country_code : FR/IT

To check whether the vehicle_owner or policy_holder appears on the document, you can optionally add checks and follow the status.

Follow the full guide on Document Analysis here

We’re introducing the Certified Identity Verification - PVID, an ANSSI‑certified remote identity verification that provides an assurance level equivalent to in‑person checks.

To launch a PVID verification, use the creation endpoint POST /verifications/identity_videos (see API reference) and set the pvid parameter to true . Then share the generated verification link with the person to verify.

What’s different vs. standard Video Identity Verification:

• Automated face and document challenges during the flow
• Systematic human review on every verification
• A dedicated “proof file” (distinct from the Audit Trail) available in case of dispute

For more information about Video Identity Verification products differences, please consult our guide.

When calling our Document Analysis endpoint, we now detect the type of uploaded document. The detected document type is returned in the field : document_type.

When the expected document type doesn't match the detected document_type, a new status code : DA_1003 is raised and the Document Analysis results to a failed status.

For more information read our full guide here.

A new custom_recipient_order parameter is available on Initiate and Update Signature Request endpoints.

When set to true, you define the execution order of all recipients together, regardless of role.

Approvers can be placed at any position in the flow, and recipients can act in parallel within an ordered sequence.

Existing behavior (custom_recipient_order = false) is unchanged. For full details, see Configure Recipient Ordering.

You can now verify the existence of a company in Spain and, when available, retrieve structured official company data.

Start a verification with the Company Verification creation endpoint POST /verifications/companies (see API reference).

• The company_number: the NIF code: 9 characters (leading letter, 7 digits, and a control character).
• Set country_code = ES

For more details on how to verify a company in Spain, please refer to our dedicated guide section here.

You can now retrieve a Verified Identity Proof in PDF format, including the ID documents used during the identification, for Qualified Electronic Signatures (QES) when the associated identification was completed through Video Verification via the endpoint GET /signature_requests/{signatureRequestId}/signers/{signerId}/verified_identity_proof/download.

This proof is available only if:

• Have at least the API PRO plan;
• the QES is successful,
• the identification was performed via Video Verification,
• the identification data has not been anonymized (the proof remains available until anonymization — currently 90 days after identification).

Not available for:

• identifications completed using a Saved Identity (no access to underlying identity documents, so the proof cannot be provided).

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

API and Webhook Log retention now depends on your plan:

For more details, see API & Webhook Logs.

We’ve shipped multiple improvements to theLogs pages in the app to help you debug faster and find the right events more easily:

• Search logs by Signature Request ID to jump straight to a specific request.
• GET requests are now recorded in the Logs.
• Open log details in a full‑page view for better readability.
• Filter logs by a custom time range.
• Choose how many results to display per page.
• Request and response bodies for multipart/form-data are now captured.
• Filter logs by API key to isolate traffic per integration.
• Access the Logs for a given Signature Request directly from its details page.

For more details, see API & Webhook Logs.