You can use Dropbox Sign Events to learn about actions that happen in Dropbox Sign as they occur. This allows you to build automations that are triggered by an event in your eSignature flow, such as a template being created, a signature request being completed, or a signature request being declined by a required signer.
Note: you may see the terms "webhooks" and "events and callbacks" used interchangeably throughout documentation on this feature. They mean the same thing.
Dropbox Sign Events, or webhooks, are messages about an event that are sent via POST request from Dropbox Sign's servers to a user-defined callback url. They allow Dropbox Sign to automatically send real-time event data to your app when triggered by an event (like a document being signed). You can think of webhooks as push notifications for servers.
multipart/form-data POST requests. Some programming languages may require middleware tooling to parse the request and get to the message. More detailed information is available in our Events and Callbacks Walkthrough.
Events can be sent as either App Callbacks or Account Callbacks depending on your configuration. We recommend researching both and selecting the approach that makes the most sense for your app.
Here is a list of webhook events that can be sent to your callback urls:
|Attached API object
|The signature request has been viewed.
|A signer has completed all required fields on the signature request.
|An updated version of the signed PDF is available for download.
|The signature request has been sent successfully.
|The signature request was declined by a signer.
|The signer has reassigned their signature request to a different party.
|All signers have been sent a reminder to complete the signature request.
|All signers have completed all required fields for the signature request. Reliable indicator that the final PDF is ready to be downloaded using /signature_request/files.
|An email address for one of the signers on your signature request has bounced. Can be corrected using /signature_request/update.
|An error occurred while processing the signature request data on our back-end. Can be caused by invalid text tags or other errors with data used in the signature request.
|The signature request has been canceled.
|The signature request has expired, signers who failed to sign will be marked
|The signature request has been prepared but not sent.
|The file provided in your signature request couldn't be converted.
|An unknown error occurred while processing a signature request.
|The embedded sign URL you provided is invalid or expired.
|A Dropbox Sign account created through one of your apps has been confirmed.
|A template has been created.
|There was an error while creating your template.