Improved
Set an expiration time on Signature Requests
October 19th, 2026
You can now set an expiration time, and not only a date, on your Signature Requests.
The expiration_date parameter now accepts a date and time in the YYYY-MM-DDTHH:MM:SS format, for example 2026-10-20T16:00:00. It is available on the following endpoints:
How it works:
- The time is read in the Signature Request
timezone. Do not include a time offset such asZor+02:00: the request is rejected with a400error. - Responses still return
expiration_datein UTC. Do not send this value back as is, since it includes an offset. - The date-only format
YYYY-MM-DDis still accepted. In that case, the Signature Request expires at 23:59:59 in its timezone, as before. - The validation rules are unchanged: the expiration cannot be in the past or more than one year after initiation.
- The
signature_request.expiredwebhook event is triggered once the expiration time has passed.
Available in both Production and Sandbox environments.

