It is now possible to sign a previously sealed document directly using its electronic_seal_document_id. This saves you having to download and upload a sealed document to create an SR, you can go straight to the sealed document for SR creation.

The endpoint used is POST /signature_requests/{signatureRequestId}/documents, with the new parameter here.

Please consult our dedicated guide to learn more about the Seal&Sign feature.

Users building their signing flow can now offer their users the option to upload their signature image instead of applying to the signed document the predesigned signature. To use this feature, the signature design "Uploaded signature image" needs to be activated in your signature settings.

For more information, visit our documentation.

You can now send manual email reminders to Approvers, just as you can for Signers of a Signature Request.

For more information, visit the Manual Reminder documentation.

You can now customize the text of the One-Time Password (OTP) SMS sent to signers via the Yousign API.

This feature allows you to align the OTP SMS content with your brand and provide clear instructions to your signers.

For more information, visit the Custom OTP SMS documentation.

You can now add or remove users from workspaces via the API:

• Add Users: Add users from your organization to a workspace.
• Remove Users: Remove users from a workspace unless they are the owner of the organization or it's their last workspace.

For more details, refer to our Workspaces guide.

It's now possible to upload a docx in the Signature Request. You can also replace PDF by docx and vice-versa.

To help you create even better integration with our API, we have added 3 new Webhook events:

1. signature_request.deleted to be notified when a Signature Request is deleted.
2. signature_request.canceledto be notified when a Signature Request is canceled.
3. signature_request.reactivatedto be notified when an expired Signature Request is reactivated.

Please consult our dedicated guide to learn more about Webhooks.

It's now possible to trigger actions when a signature is completed on iFrame integration.

We provide a new method onSignatureDone() on our latest iFrame SDK version (1.6.0).

This is the preferred moment if you want to download the complete document with all signatures.

For more details about how to use it, please check the iFrame SDK reference.

🔗 It’s now possible to set a custom URL to which the signer will be redirected if they decline the signature.

It can be configured:

• At Signer level in the Signer creation endpoint POST/signature_requests/{id}/signers (see API reference).
• In the Custom Experience; either in the web app or via API in the Custom Experience creation endpoint POST/custom_experiences (see API reference).

Learn more about how to redirect a Signer at the end of the signing flow here.

To enhance security and protect against potential threats, a paid plan is now required to configure redirect URLs.

Consult this page to learn more about this feature.