Documents from a Signature Request can now be downloaded one by one. All you need to do is use this endpoint and provide the signatureRequestId and the documentId. A .pdf file will be sent as a response.

It is now possible to manage your Custom Experiences from the API, in addition to the application.
You no longer need to use the Yousign application to create and modify your Custom Experiences: it is now possible to do so directly from the API! You can find all your creations in your application.

New endpoints to use:

POST /custom_experience
GET /custom_experience
PATCH /custom_experience
DELETE /custom_experience

Link to the dedicated page on the documentation: https://developers.yousign.com/docs/custom-experiences-new

We talk about the Custom Experience and no more Branding.

🤔 Why?
Because the word Branding is not wide enough to designate everything that can be set-up. The term Custom Experience is more appropriate and reflect in-app naming.

So, this change is expected to be reflected in the API code.

Technical change:

branding_id it's replace by custom_experience_id in signature_requests payload and responses.

branding_id is deprecated but you don't need to change anything in your code, it will still work and it is not planned to be suppressed.
It is the new property name and it should be used for new implementations.