For users of our Electronic Seal with the Advanced level, it is now possible to specify which certificate you want to use when performing the Sealing operation. This is done by passing an optional certificate_id field when Creating an Electronic Seal.

Note that the generation of Advanced Seal certificates is a process which requires identification documents for your company and its representatives. Please contact your Yousign customer representative for more information on this topic.

As we know your business can scale, you might need a higher Rate-limit for our API usage.

If your implementation respects our standards (mainly use Webhooks instead of massive polling), you can fill a customisation request available at the bottom of Limits page

Radio buttons are a useful and easy way to present a set of options to Signers and allow them to select one choice.

Today, we are introducing mechanisms that enable easy retrieval of selected options, if any. This will help you to build custom integration and behavior based on the Signer choice.

Radio and Radio Group now have name property

When adding Signer with a Radio Group Field, you can optionally set name in radiogroup and radio to better identify your Fields.

Manual Creation

In Signer's creation payload

A code sample can also be found in the Radio Button Field Guide

Smart Anchor creation

Here is the new syntax for Radio Group Smart Anchor. All details can be found in our documentation
{{s1|radio|28|group_name|t|radio_name_1}} {{s1|radio|28|group_name|t|radio_name_2}}

Returned payload

Those values are also returned in Signer's Field payloads

Radio names and values are now returned in the webhook payload

When returning radio data in a Webhook call, it now also contains name and checked in Signer's payload

This payload can also be found in signature_request , signer , and approver webhook Events, under signers > answers.

Followers can now be listed using the API. The endpoint details can be found here.

follower_link is available in both endpoints List Followers and Add Followers

Please note that follower_link is

• null if the Signature Request is not activated
• valued with the follower link if the Signature Request is activated

Metadata allows you to attach extra information to your Signature Requests. Our customers generally use it to provide specific context to their business.

More information about how to use metadata can be found in our dedicated guide section.

You will also find in the API reference the extensive endpoints list related to metadata.

2 new locale de andit are available for your audit trails.

You can now choose between en, fr, es, de or it.

By default, en will be used (current behavior).

This option can be set on Signature Requests with audit_trail_locale field.

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.

Contacts can now be updated using the API. The endpoint details can be found here.

It is also possible to manage Contacts from the application.

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.

🚧

Warning

These changes are effective since 18/10/2023.