:runner: List Signature Requests

:bug: Bugs Fixed

  • iFrames: In sanbox mode, setting the disable_domain_validation parameter to true now correctly allows any referrer by returning the response header frame-ancestors: *.

🗑️ Signature Request can now be permanently delete

We've improved the existing delete endpoint, by adding the new permanent_delete parameter:

  • If the permanent_delete parameter is set on false (by default), the Signature Request is deleted.
  • If the permanent_delete parameter is set on true, the Signature Request is permanently deleted and can’t be retrieved.

More information about the feature can be found in our guide.

You will also find in the API reference more details about the endpoint.

:star2: Fields Management Endpoint

A whole new set of CRUD endpoints are available for Fields management. More information on the API Reference

:bug: Bugs Fixed

  • Smart Anchor detection improvement in Documents.
  • custom_note is no longer mandatory when calling Cancel a Signature Request
  • Add "declined" to List Signature Request status list in API Reference

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