How to get app approval for Dropbox Sign API

To ensure that your Dropbox Sign app integrations adhere to signature regulations and best practices, an app approval is needed prior to your project going live.

Note: If you’re implementing a non-embedded workflow, you don’t need to complete the app approval process. Simply remove the "test_mode" flag from your code to start making live requests.

Using an embedded workflow

If you’re using embedded signing, embedded requesting, or embedded templates, you can self-publish your own API app once you’re ready to move to production. Approval will be instant.

Learn more about self-publishing API apps.

Note: The self-publish option has a limit of 10 API apps.

Using an OAuth workflow

If you’re using OAuth workflows, you’ll need to submit your app for approval by filling out the relevant OAuth Workflow App Approval Form for your workflow. If you're using both OAuth and embedded workflows, you only need to fill out the OAuth workflow form.

Follow these guidelines for preparing your materials for approval.

Note: Only live activity requires approval. You can still use your app in test mode until it gets approved. You can complete the app approval process prior to signing up for a paid plan, but you won’t be able to make production calls until a paid plan is activated.

We perform app reviews to check whether the Dropbox Sign API was implemented correctly, and to catch potential problems before your app goes into production.

If your app is not initially approved, our support engineering team will reach out to you directly to assist with any issues, or provide support on workflow best practices if needed.

Learn more about the app approval process.

If you have questions, you can create a ticket with our API Support Team.