You can now view your API rate limits directly from the new Rate Limits page in the Developers section.

This page makes it easier to check your current limits in Production and Sandbox, anticipate usage, and request an increase when needed.

A new Rate Limits documentation page is also available, containing updated guidelines and best practices to stay within limits.

You can now add a text caption directly inside an Electronic Seal Field area using the new captions parameter on POST /v3/electronic_seals (see API reference).

The caption is rendered below the seal image, within the same Field area. It is useful to display a short label tied to the seal visual — such as a department name or internal reference — without placing a separate read_only_text Field next to it. Unlike read_only_text, it can be used on already-signed documents without breaking prior signatures.

Key constraints:

• captions accepts an array with exactly one entry.
• text must not exceed 150 characters.
• Font size is calculated automatically to fit the available space; adjust the size of your image, width or height parameters to control line wrapping.
• The parameter is optional, omit it entirely to render no caption.

For full details, see the Add Caption to your Electronic Seal guide.

It is now possible to iFrame Workflow Collect for an embedded experience at low development cost. iFraming Workflow Collect works similarly with iFraming the signature flow.

When iFraming Workflow Collect, we emit the following events to help you manage the integration :

• started: the Applicant has opened the Workflow Session Link.
• processed: the Applicant has comlpeted all Actions successfully and has no additional actions to take.
• blocked: the Applicant has reached the limite of retries for a given verification and can no longer upload documents for verification.
• ping : Workflow Session link is loaded.

To learn more about how to iFrame Workflow Collect, follow our complete guide here.

You can now analyze French tax notices with Request a Document Analysis. This helps you automate income verification and extract key tax notice data from supported documents.

For the tax_notice document type, Document Analysis now extracts:

• fiscalNumber1
• fiscalNumber2
• taxNoticeReference
• issuanceDate
• incomeYear
• referenceIncome

You can also send optional consistency-check parameters when creating the analysis:

• first_name — checks that the provided first name matches the document
• last_name — checks that the provided last name matches the document
• income_year — specifies the tax filing period

To learn more, see the Document Analysis guide.

We're introducing new dedicated Webhook events to help you follow more efficiently the status of an Applicant inside a Workflow Session.

• applicant.notified: triggered when a Workflow Session Link has been generated for your applicant.
• applicant.processed: triggered when your Applicant has completed all the attached verifications and has no additional action to take.
• applicant.session_blocked: triggered when an Applicant is blockedand can't perform any additional actions on the Workflow Session Link.

Read the full documentation here

You can now enforce business rules when creating an Image Identity Verification. Configure the new parameters with the request endpoint POST /verifications/identity_documents (see API reference):

• min_age - minimum accepted age
• max_age - maximum accepted age
• prohibited_countries - list of issuing countries to reject

If a configured rule is not met, the verification returns a failed status with a dedicated status code.

See the status code mapping on this page, and learn how to configure these checks in the guide.

You can now reuse a decision from the Image Identity Verification endpoint (see the reference) to complete one Advanced Electronic Signature (AES). This avoids running a second verification when initiating the AES.

How it works:

• First, perform an Image Identity Verification and keep the decision ID from the response (see the reference). Please not, for the moment, verification via Video Check (see the reference) cannot be reused in an AES context.
  • Identification must be verified;
  • And must be used within 7 days, otherwise the Signature Request will be cancelled in full because the identification associated for a Signer will be anonymised.
• When you initiate the AES with the Signature Request creation endpoint POST /signature_requests/{signatureRequestId}/signers, include that ID in the payload via the verified_identity_id parameter (see API reference).

To access this feature, you must have at least a PRO API plan and contact a sales representative to activate access to this endpoint for your organisation.

For more information about the feature, you can consult our dedicated guide.

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