A Fail-Fast Policy Update: Accelerated Webhook Timeout

The initial webhook timeouts will change from 10 seconds to 0.5 seconds, and retries will still
have a 10-second timeout. If a webhook fails on the first attempt due to a response taking too long, it will still be retried as explained in our Failure and Retry Policy.

The webhook timeouts evolution will affect you if:

• If your webhook endpoints take over 0.5 seconds to respond.
• If you don't verify webhook uniqueness upon receipt.

If either applies to you, we recommend adjusting your webhook setup.

When your initial webhook response takes more than 0.5 seconds, it might trigger a retry, even if it is processed correctly on your side, potentially leading to duplicates. To prevent this:

• Send the response status as soon as possible.
• Save the event_id attribute available in payload to ensure its uniqueness.

Take a moment to review our dedicated guide to better understand these changes.

🚧

Warning

These changes are effective since 18/10/2023.

We're thrilled to announce that the Qualified Electronic Signature (QES) by Yousign is finally out!

QES is the highest level of electronic signature.

We are proud to introduce to the market the simplest QES experience, certified by ANSSI in France. Note that our QES is available all across Europe.

Why Yousign's QES is the simplest?

• Invite your signers with a few clicks, as you do for other levels
• Signers will have to perform a strong authentication thanks to their physical identity document and a video of their face in real time.

Good to know Signers will then have the possibility to register their identity on their own smartphone, to sign their next QES faster --> No application download is needed, it simply works thanks to a secured QR code.

• Recurrent signers will be able to use their saved identity stored on their smartphone, to sign in less than 2 minutes! A QES has never been signed so fast!

How to access it?

If you wish to use this level on API, please contact our sales team. Get more information on the QES by Yousign on our Website.

After activating the QES level on your subscription, simply follow the QES level page to set up and test your implementation.

It is now possible to:

• Create in the application Templates in our Sandbox environment
• View, in the application, Templates created in Sandbox
• Create Signature Requests in Sandbox, based on Templates

The documentation is available here.

Electronic Seal Images management has been improved. Besides upload, it is now possible to list, download and delete the Electronic Seal Images of your organization.

Note that this improvement is available for all levels of Electronic Seal (simple and advanced).

It’s now possible to customise the Signature Request sender name with our API. The customisation is possible in the end-point POST /signature_requests.

3 options are available :

• The sender will have the organisation's name.
• The sender will have the workspace's name.
• The sender will have a custom value

This change affects:

• The email sender, subject and signature.
• The text displayed in the email body.

Here is a payload example using the sender's custom value.

{
  "name": "New Signature Request",
  "delivery_mode": "email",
  "reminder_settings": {
    "interval_in_days": 1
  },
  "email_notification": {
    "sender": {
      "type": "custom",
      "custom_name": "A very custom sender name"
    }
  }
}

A new locale es is now available for your audit trails.

You can now choose between en, fr and es.
By default, en will be used (current behaviour).

This option can be set on Signature Requests

A new option on Signature Requests is now available to allow Signers to decline a signature during the signing flow: signers_allowed_to_decline. This field is set to false by default.

To be able to use this feature, you will first have to activate it globally for your organization, within the application settings page.

With this new feature, we are introducing the new declined status for Signature Requests and Signers. You can listen to the declining event using the dedicated Webhooks: signature_request.declined and signer.declined. The payload of these Webhooks will contain the signer that declined, as well as their reason for declining.

It is now possible to re-order documents within a Signature Request in draft status.

If you add several documents to your Signature Request, you may want to choose which one is presented first to the Signer.

By default, documents will be presented by the upload date, from the oldest to the most recent.

It is also possible to override this rule by specifying after which document a specific document should be displayed. To do that, you need to use the field insert_after_id, available in our endpoint to upload or update a document.

The Advanced Electronic Seal is now available through the Yousign API!
It allows organizations (legal persons) to seal documents without requiring the actions linked to a signature process. It helps reduce the risk of fraud and proves document integrity.
In addition to simpler use cases, we advise using this seal level in particular for payslips and digitization of paper invoices or paper expense reports.

Please reach out to your customer representative to activate this product on your account.

Guide

https://developers.yousign.com/docs/electronic-seal-1

Endpoint

https://developers.yousign.com/reference/post-electronic-seals

A new option on Signature Requests is now available to define the locale of generated audit trails.

You can choose between en and fr. By default, en will be used (current behaviour).