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

You can now change a Signer’s authentication mode after activation, as long as the Signature Request’s signature_level is Simple eSignature (electronic_signature), and the Signer is in status initiated or notified. This capability does not apply to Advanced or Qualified eSignatures (AES/QES).

If you modify the OTP mode while the Signer is on the authentication step, any code already sent is invalidated, and the new method applies.

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

You can now use our Document Analysis endpoint endpoint to extract and check data for KBIS documents.

To request a new Document Analysis from a KBIS 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 use the issuance date of the document to check whether the document is older then 3 months which is the validity period for a KBIS document.

To help you better understand the results of those checks we are adding status codes to the Document Analysis endpoint (more details here).

You can now control what appears inside a Signature Field with the new display parameter.

Set display.layout to detailed to add the Signer’s full name, email, and signature date directly within the Signature Field.

When detailed, you can personalize the date and time format.

Available on Field creation in POST /signature_requests/{signatureRequestId}/documents/{documentId}/fields (see API reference).

You can now use our Company Verification endpoint to verify a German company.

To verify a company in Germany you can simply call our endpoint with

• country_code = DE
• Thecompany_name you are trying to verify
• The company_number .

For more details on how to verify a company in Germany, checkout our dedicated guide section here.

We have added a new UNKNOWN error reason to the list of QES identification errors to improve our resilience system with our provider.

• This error is returned when an inconsistency occurs with our identity provider — for example, due to a breaking change in the managed error codes, or when an unexpected empty value is received.

More details about QES errors are available in our documentation here.

You can now verify whether a bank account belongs to a given personal account holder by comparing their name with the one retrieved from the bank.

To use this feature, provide the first_name and last_name fields when calling the endpoint [POST /verifications/bank_account_connections].

Yousign automatically compares these values with the bank account holder’s name and returns a failed status if the match is below the minimum acceptable level.

For more details about comparison rules and match levels, please refer to our dedicated guide.

With checks, you can now compare if a Document belongs to a given person by comparing their information with extracted data.

To use checks, add the optional checks object when requesting a new Document Analysis (see endpoint). Yousign will then compare input data with the extracted data and return a failed status if the data don't match at the minimum acceptable level.

For more details on comparison rules and match levels, please read the following guide.

We have released a new Workflow Dashboard that allows you to monitor Workflow sessions directly in our app. This feature brings visibility to processes that were previously only available via the API.

What you can do with the Workflow Dashboard:
• View all Workflow sessions with their current status (completed, awaiting, blocked).
• Track the progress of each action, including Identity Verification, Bank Account Verification, Company Verification, Proof of Address, Watchlist Screening, and Signature Requests.
• Access clear visual indicators for each step.

Who can access it?
The Workflow Dashboard is visible in the app menu for API customers and API trial users with the Admin or Owner role.
To get started, you need to create a Workflow Template.

Important note
The Workflow Dashboard provides monitoring and visibility only. Workflow orchestration still needs to be managed through API calls.

👉 Learn more in our dedicated guide section.

With this new service we provide our customers with a simple way to accurately extract data from a document.

Right now we only support two types of documents :

• French Social Welfare Card.
• French Social Welfare Certificate.

But support for more documents are coming soon. To use this service, simply call the following endpoint by specifying the type :

• social_security

For more details on the service’s capabilities and implementation, check the full guide here.