Dropbox Sign

Dropbox Sign (formerly HelloSign) is an e-signature platform that lets you send, sign, and track legally binding documents. Its REST API exposes signature requests, account and API app management, bulk send jobs, and fax operations, so you can automate signing workflows and keep signature and account data in sync with your other systems.

Power end-to-end data operations for your Dropbox Sign API with Nexla. Our bi-directional Dropbox Sign connector is purpose-built for Dropbox Sign, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Dropbox Sign or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Dropbox Sign workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Dropbox Sign credential, you need an API key from your Dropbox Sign account. Dropbox Sign authenticates API requests using your API key, which can be supplied either as a bearer token or as the username in HTTP Basic authentication (with a blank password). Every Dropbox Sign account can hold up to four API keys at a time.

To obtain your API key, follow these steps:

1. Sign in to your Dropbox Sign account at sign.dropbox.com.

2. Click your avatar in the upper-right corner, then click Settings.

3. Open the API tab to view your API Settings page.

4. Under API keys, click Reveal Key to display an existing key, or click Create Key if you are generating your first API key.

5. Copy the API key value and store it securely, as it grants access to your Dropbox Sign account and should be treated as a secret.

If your workflow requires embedded signing or OAuth, you may also need a Client ID, which is created under API apps on the same API Settings page. For complete details about authentication and available endpoints, see the Dropbox Sign API Reference.

Authenticate

Credentials required

Api Key

An authentication method that requires sending a unique secret token with each API request

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests

Basic Authentication

A standard authentication method that requires sending encoded username and password credentials

Field	Required	Secret	Description
Username Or API Key	Yes	No	Your username or personal API Key
Password	Yes	Yes	Your password

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Select the authentication method you want to use, and enter the required values:

   • Api Key: Enter your Dropbox Sign API key in the API Key Value field. This key is sent as a bearer token to authenticate every API request and must be kept confidential.

   • Basic Authentication: Enter your Dropbox Sign API key (or account username) in the Username Or API Key field, and your password in the Password field. When authenticating with an API key, the password can be left blank.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

If your API key is compromised, revoke it from the API tab of your Dropbox Sign API Settings page and generate a new one. For more information about authentication, see the Dropbox Sign API Reference.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Dropbox Sign connector tile, then select the credential that will be used to connect to Dropbox Sign, and click Next; or, create a new Dropbox Sign credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Dropbox Sign endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get account

This endpoint template retrieves the account details associated with your Dropbox Sign credential. Use it to read account settings, quotas, and profile information.

• Optionally provide an Account Id or Email Address to look up a specific account; leave both blank to return the account tied to your credential.

Create account

This endpoint template creates a new Dropbox Sign account. Use it to provision accounts programmatically, for example when onboarding users into an embedded or white-labeled application.

• Supply the new account details, such as Email Address and Locale, along with the Client Id and Client Secret of the API app when creating accounts on behalf of an application.

Update account

This endpoint template updates the account settings associated with your Dropbox Sign credential. Use it to change account-level configuration such as the callback URL or locale.

• Provide the fields you want to change, such as Account Id, Callback Url, or Locale.

Verify account

This endpoint template checks whether a Dropbox Sign account exists for a given email address. Use it to confirm that a user has a Dropbox Sign account before initiating a workflow.

• Provide the Email Address to verify.

Get API app

This endpoint template retrieves the details of a single API app by its client ID. Use it to inspect an existing API app's configuration.

• Provide the Client Id of the API app you want to retrieve.

List API apps

This endpoint template retrieves a list of the API apps owned by your account. Use it to enumerate API apps for auditing or management purposes.

• Optionally provide Page and Page Size parameters to page through large result sets.

Create API app

This endpoint template creates a new API app on your Dropbox Sign account. Use it to register an application that can embed signing or use OAuth.

• Supply the API app configuration, such as Name, Domains, Callback Url, and any OAuth or white-labeling options.

Update API app

This endpoint template updates the configuration of an existing API app, identified by its client ID. Use it to change settings such as the callback URL, domains, or OAuth options.

• Provide the Client Id of the API app along with the fields you want to change.

Get bulk send job

This endpoint template retrieves the signature requests belonging to a bulk send job, identified by its job ID. Use it to track the status of documents sent through a bulk send operation.

• Provide the Bulk Send Job Id, and optionally Page and Page Size to page through the results.

List bulk send jobs

This endpoint template retrieves a list of the bulk send jobs on your account. Use it to enumerate past and in-progress bulk send operations for reporting or monitoring.

• Optionally provide Page and Page Size parameters to page through large result sets.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Dropbox Sign data sources can also be manually configured to ingest data from any valid Dropbox Sign API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Dropbox Sign data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Dropbox Sign destination, and select the Send to Destination option from the menu. Select the Dropbox Sign connector from the list of available destination connectors, then select the credential that will be used to connect to Dropbox Sign, and click Next; or, create a new Dropbox Sign credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Dropbox Sign endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Cancel signature request

This endpoint template cancels an incomplete signature request, identified by its signature request ID. Use it to stop pending signature requests that are no longer needed.

• Each record from your Nexset should provide the Signature Request Id of the request to cancel.

Resend an API notification

This endpoint template resends an API notification (callback) asynchronously. Use it to retry event callbacks that your application may have missed.

• Each record from your Nexset is sent as the request body to trigger the notification retry.

Delete API app

This endpoint template deletes an API app, identified by its client ID. Use it to remove API apps that are no longer in use.

• Each record from your Nexset should provide the Client Id of the API app to delete.

Create fax line

This endpoint template purchases and creates a new fax line. Use it to provision fax numbers programmatically.

• Provide the fax line details, such as Area Code, Country, City, and Account Id.

Delete fax line

This endpoint template deletes an existing fax line. Use it to release fax numbers you no longer need.

• Each record from your Nexset should provide the Number of the fax line to delete.

Add user to fax line

This endpoint template grants a user access to a fax line. Use it to share a fax number with additional team members.

• Provide the fax line Number and the user to add, identified by Account Id or Email Address.

Remove user from fax line

This endpoint template revokes a user's access to a fax line. Use it to remove team members from a shared fax number.

• Provide the fax line Number and the user to remove, identified by Account Id or Email Address.

Delete fax

This endpoint template deletes a fax, identified by its fax ID. Use it to remove stored faxes that are no longer needed.

• Each record from your Nexset should provide the Fax Id of the fax to delete.

Generate OAuth token

This endpoint template exchanges an authorization code for an OAuth access token. Use it as part of an OAuth authorization flow for an API app.

• Provide the required OAuth parameters, such as Client Id, Client Secret, Code, Grant Type, and State.

Refresh OAuth token

This endpoint template refreshes an expired OAuth access token using a refresh token. Use it to keep an API app's OAuth session active without re-authorizing.

• Provide the required OAuth parameters, such as Grant Type, Refresh Token, Client Id, and Client Secret.

Manual configuration

Dropbox Sign destinations can also be manually configured to send data to any valid Dropbox Sign API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Dropbox Sign APIs typically expect JSON format for most operations. For operations that act on a specific object, include the object's ID in the endpoint URL as required by the endpoint.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Dropbox Sign endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Dropbox Sign endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.