❓

What is a Read-Only Text Field?

Read-Only Text Fields allow you to add text on a document that won't be editable by any of the recipients. It's a way to quickly edit the document before sending it for signature.

✏️ Those Read-Only Text Field can be let empty on a Template

Those fields will have to be populated when a new request is created from the Template. This feature is particularly useful when certain document details, such as prices or terms, need to be customised for each request.

These empty Read-Only Text Fields should be populated with the required text in the payload of the Signature Request initiation endpoint POST /signature_requests (see API reference).

For more details on how to use empty Read-Only Text Fields in your templates, refer to our guide section.

It is now possible to create a Signature Request with the option to collect documents (such as banking or residence documents) from the Signers with this new endpoint.
Once the status of the Signer is Signed and the required documents are uploaded, you will be able to

• List the Signer Documents
• Download the Signer Documents
• Delete the Signer Documents

You will find additional information about the feature in our guide.

🎨 Yousign's API now allows signing a Signature Request without asking Signers to go through Yousign's pre-made signing flow (in an iFrame or directly on Yousign's platform).

Indeed, you have the opportunity to build your own signing flow, matching your needs. This is particularly useful if:

• You want to build a custom signing flow.
• You need to interface with physical devices to collect signatures (such as a signature pad for example).
• You need to integrate the signing flow into a mobile application, without using Yousign's iFrame or being redirected to Yousign's platform.

For comprehensive instructions on how to use this feature, please refer to our dedicated guide section. A code example is also available.

It is now possible to create a Signature Request from a Template that contains a Placeholder Signer.

❓

What is a Placeholder Signer?

It is a special type of Signer that can be added to a Template. Opting for this type of Signer is suitable if a different person will sign each time a Signature Request is created.

Those Placeholder Signers can be directly replaced by “real” Signers in the payload of the Signature Request initiation endpoint POST /signature_requests (see API reference).

You will find more information on how to leverage Placeholder Signers in our guide section.

🎨 Fields now support custom font families, sizes, and colours.

The following field types now support the font object property: Mention, Text, and Read-only Text.

We have added support for the following font families:

• Inconsolata
• Open Sans
• Lato
• Raleway
• Merriweather
• EB Garamond
• Comic Neue

Bold and italic styles are now also supported, along with custom font sizes and colours 🎨.

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

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

🏃 List Signature Requests

• List all Signature Requests: Added a new limit query parameter to limit the number of items to retrieve for better performances

🐛 Bugs Fixed

• iFrames: In Sandbox 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.

🌟 Read-only Text fields

It is now possible to create Signature Requests containing Read-only Text fields using our API.

You will find more information on how they can help you in our guide section. An example is also available.

🌟 Fields Management Endpoint

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

🐛 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

Starting today, 15th February, each of our environments (sandbox and production) will have different rate limit values.

The new policy is detailed in our documentation.