Events Overview
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.
What are Dropbox Sign Events
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.
How Events Are Sent
Events are sent as 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.
Dropbox Sign notifies your app when a Signature Request or Template event happens involving your account.
Dropbox Sign notifies your app when a Signature Request, Template, or Account event happens involving a specific API App.
Event Names
Here is a list of webhook events that can be sent to your callback urls:
Securing your Callback Handler
Reference our section on securing your callback handler, in the Events Walkthrough, for steps you can take to ensure that your callback handler is safe.