Manage callbacks in Dropbox Sign

Your API app is configured and ready to support your integration. But your application also needs a way to know when something changes, such as a document being signed, declined, or completed.

Dropbox Sign can notify your application automatically whenever these events occur.

In this module, you'll learn how callbacks keep your application synchronized with Dropbox Sign activity and how they support automated workflows without constantly checking for updates.

What are callbacks

Callbacks, also known as webhooks, allow Dropbox Sign to notify your systems when important events occur.

Instead of continuously checking Dropbox Sign for updates, your application can receive information automatically when activity takes place.

Think of callbacks as event notifications that help keep your systems synchronized with Dropbox Sign.

Why use callbacks

Callbacks allow your application to respond automatically to activity occurring within Dropbox Sign.

Common examples include

Document completed

A signed document is finalized and your application updates its status automatically.

Document declined

A signer declines a request and your workflow notifies the appropriate team.

Signature request sent

A request is successfully delivered and your system records the event.

Signature request completed

All required signers have completed the request, allowing your application to continue the workflow, such as notifying another system or preparing to retrieve the completed document.

Other common events

Depending on your workflow, callbacks can also help track:

• Document viewed

• Signature request completed

• Completed document available

• Signature request canceled

• Signer reassigned

Callbacks help eliminate manual tracking and support automated workflows.

How callbacks support integrations

Without callbacks, applications often need to repeatedly query Dropbox Sign to check for updates.

With callbacks: Dropbox Sign → Event occurs → Callback sent → Your application updates

This allows systems to react quickly and reduces unnecessary API requests.

Common use cases

Organizations often use callbacks to:

• Update CRM records

• Trigger workflow automation

• Notify internal teams

• Synchronize business systems

• Generate audit records

Testing your callback URL

Before moving your integration to production, test your callback URL to verify it's receiving and processing events correctly.

Dropbox Sign provides a test option in the callback settings, allowing you to send a test event and confirm that your integration is responding as expected.

Note

For Dropbox Sign to recognize that a callback has been received successfully, your callback handler must return an HTTP 200 response with the response body: Hello API Event Received

If the expected response isn't returned, Dropbox Sign treats the callback as failed and retries the request. This is one of the most common causes of callback issues when setting up a new integration.

Account-level callbacks

Account-level callbacks track activity across your Dropbox Sign account.

When configured, Dropbox Sign sends event notifications for activity occurring throughout the account.

When should you use account-level callbacks?

Account-level callbacks are useful when you need visibility into:

• Organization-wide activity

• Multiple integrations

• All signature workflows

Examples:

• Centralized reporting systems

• Enterprise monitoring solutions

• Organization-wide automation workflows

App-level callbacks

App-level callbacks are associated with a specific API app. Only activity related to that application triggers callback notifications.

When a request is made through an API app, Dropbox Sign sends callback events to that app's callback URL rather than the account-level callback URL.

When should you use app-level callbacks?

App-level callbacks are useful when:

• Multiple integrations exist.

• Different applications require separate event handling.

• Teams manage independent integrations.

Examples:

• Customer portal integration

• HR onboarding platform

• Contract management system

Each application can receive and process only the events relevant to its own workflows.

Account callback vs app callback

Choosing the correct callback type depends on the visibility you need.

• Choose an account callback if you want to track activity across your entire Dropbox Sign account.

• Choose an app callback if you only want to track activity for a specific API app or integration.

Example:

An organization with a single integration may choose an account callback to monitor all Dropbox Sign activity in one place.

An organization managing separate HR, Sales, and Operations integrations may prefer app callbacks so each application receives only the events relevant to its own workflow.

Integration tip

Think about how your integrations might grow over time. Choosing the right callback type early can simplify administration and make it easier to manage multiple applications as your environment expands.

Planning your callback strategy

Before configuring callbacks, consider:

• How many integrations will be deployed?

• Which systems need event notifications?

• Will multiple teams manage separate applications?

• Do events need to be centralized or isolated?

Answering these questions can help you select the most appropriate callback architecture.

Best practice

Document callback ownership and destinations as part of your integration documentation.

This makes troubleshooting and future maintenance easier as integrations evolve.

Your integration can now respond automatically to the events that matter most, creating a more connected and automated workflow.