Submitting for App Approval

Dropbox Sign requires approval for certain apps before they can be used in production. This page contains guidance on submitting your Dropbox Sign app for review and approval through our Support Assisted Approval process. The submission forms are at the bottom of the page.

Before You Submit

We recommend gathering the information needed to complete the app approval request prior to starting the form:

Embedded and OAuth Workflow Differences

The submission requirements will differ depending on whether your app uses an Embedded workflow or Dropbox Sign OAuth. There are separate forms for each workflows and you only need to submit the form that applies to your app. If your app uses both the Embedded workflow and Dropbox Sign OAuth, then you will only need to submit the OAuth approval form.

Items required for the Embedded Workflow Form:

• Website URL
• Client ID(s) for the apps you’re requesting approval for
• A link to a screen recording that demonstrates your integration (see Recording a Demo - Apps Using Embedded Features)
  • Relevant identifiers associated with the demo, i.e. signature_request_id and or template_id used in the demo
  • A list of the endpoints used in the demo

Items required for the OAuth Workflow Form:

• Website URL
• Client ID(s) for the apps you’re requesting approval for
• The billing and access scopes that are enabled for your app
  • User Pays Scopes
    • Account Access
    • Signature Request Access
    • Template Access
    • Team Access
    • API App Access
  • App Owner Pays Scopes
    • Basic Account Info
    • Sending Signature Requests
• A link to a screen recorded demo of your integration (see Recording a Demo - Apps Using OAuth Features)
  • Relevant identifiers associated with the demo, i.e. signature_request_id and or template_id used in the demo
  • A list of the endpoints used in the demo
• A description of how you are using all enabled scopes not shown in the demo recording

Plan Your Demo

While completing the request form you’ll be asked to provide a URL to a screen recorded demo of your integration. We recommend creating a plan and recording the demo video before filling out the submission form. More details on what is required for the demo video can be found in the Recording a Demo section below.

Recording a Demo

Your app approval request must include a link to a screen recording that demonstrates your integration. The URL to the recording should be included in the submission form.

A great demo video will typically be 3-5 minutes long, includes a clear voiceover, and walks through the use of implemented Dropbox Sign features from start to finish. The demo only needs to show the Dropbox Sign workflows you are using, it does not need to be a complete overview of your platform. The demo requirements will vary depending on the integration type (Embedded or OAuth), and these are broken down accordingly below:

Apps Using Embedded Features

The demo should show all of Dropbox Sign’s embedded features implemented in your app. Please make sure to demonstrate the entire workflow for each embedded feature from start to finish.

Here is a list of steps that should be demonstrated for each respective embedded feature that you are using:

Keep track of your Signature Request ID, Template ID, or any relevant identifiers used in the demo. You’ll need those for submission.

Apps Using OAuth Features

Steps that should be demonstrated in the OAuth demo video include:

• A user completing an OAuth flow and authorizing your app to interact with the Dropbox Sign API on their behalf.
  • Note: this must be completed from your own account since this demo is in test mode.
• Demonstrate how you will use each of the scopes you have enabled.
  • User Pays Scopes
    • Account Access
    • Signature Request Access
    • Template Access
    • Team Access
    • API App Access
  • App Owner Pays Scopes
    • Basic Account Info
    • Sending Signature Requests

Keep track of your Signature Request ID, Template ID, or any relevant identifiers used in the demo. You’ll need those for submission.

Apps that use both Embedded and OAuth

If you are using both the Embedded and OAuth implementations, please follow the demo requirements for Apps Using OAuth Features found above.

Submitting the Approval Approval Request Form

You can submit your app for approval by filling out the relevant app approval form (Embedded or OAuth) for your workflow. If you are using both OAuth and Embedded, you only need to fill out the OAuth workflow form.

For implementations using an Embedded workflow, please fill out this form and provide the link to your demo video.

• Embedded Workflow App Approval Form

For implementations using an OAuth workflow (or OAuth and Embedded), please fill out this form and provide the link to your demo video.

• OAuth Workflow App Approval Form

We’re here to help! Let us know if you have any questions by opening a support ticket with our API support team.