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.
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
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.
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.
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.
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.
