It is now possible to add multi-line mention fields in Signature Requests sent with our API.

Currently, this option is only available for manual fields and is not yet available for Smart Anchors.

Two options are offered:

  • Set a specific height
  • Let the height be automatically computed based on the number of line breaks in the mention content.

More details are available in our documentation.

When an ongoing Signature Request using the delivery mode : none has the email address from a Signer updated, the previously generated Magic Link is not valid anymore.

If you update a Signer's or an Approver's email address after the Signature Request activation, the previously sent signature link for this specific signer will be disabled. You will have to fetch the new Signature Link and it again to the Signature Request participant.

More information about the delivery mode :none and signature links can be found here

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.



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

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"