*** title: Dropbox Sign API Documentation description: >- The Dropbox Sign API offers a reliable, flexible set of eSignature tools that can be used to power digital agreements and turn slow, outdated business processes into a competitive advantage. 'og:description': >- The Dropbox Sign API offers a reliable, flexible set of eSignature tools that can be used to power digital agreements and turn slow, outdated business processes into a competitive advantage. --------------------------------------- Test how easy it is to customize and sign a document—try the [demo](https://app.hellosign.com/api/white-labeling).
The Dropbox Sign API offers a reliable, flexible set of eSignature tools that can be used to power digital agreements and turn slow, outdated business processes into a competitive advantage. With a broad range of highly-configurable [features](https://www.hellosign.com/products/api/features), the Dropbox Sign API empowers you to build secure signing experiences and document workflows that delight your users. This documentation contains information and resources to help you build with the Dropbox Sign API. Here's some of what you'll find here: * **API Reference** - comprehensive technical information and code examples for the entire Dropbox Sign API. Includes a *Try it console* to explore and test endpoints by sending API calls directly from the docs. * **Guides / Walkthroughs** - in-depth information and tutorials about features, concepts, and use cases. * **Libraries** - links to official Dropbox Sign SDKs.
Try it console demo
*** ## Testing the Dropbox Sign API You can fully test every endpoint and *almost* every feature in the Dropbox Sign API (even from a [free account](https://app.hellosign.com/api/pricing)) by setting `test_mode` to `true` on your API requests. There are a few key behaviors to be aware of: * Signature requests created in `test_mode` are **not legally binding** and documents are watermarked as such. * Signature requests submitted in `test_mode` will be visible in the Dropbox Sign accounts of requester and signers. Please consider the e-mail addresses you use when testing. * You can add [custom branding](/api/manual-reference-pages/premium-branding) that will be applied to calls sent with `test_mode`. However, production requests will ignore those settings unless you're subscribed to a [Standard or Premium plan](https://app.hellosign.com/api/pricing). *** ## How we charge Sending production (legally-binding) signature requests requires a [paid API plan](https://app.hellosign.com/api/pricing). The API will return a status code of `402` if such requests are made without a proper plan. We understand that you may want to test the API before paying for it. Some API endpoints are restricted to paid plans, but can still be used without signing up for a paid plan by using our test mode. See the [Testing section](#testing-the-dropbox-sign-api) above. ### Endpoints by subscription plan The endpoints below are organized by the subscription plan required to use them. | Required Plan | Notes | | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Free | build with all endpoints using `test_mode` | | Essentials | Access to signature request endpoints. Can use templates created on Dropbox Sign website.
[signature\_request/send](/api/signature-request/send)
[signature\_request/send\_with\_template](/api/signature-request/send-with-template) | | Standard | Access to bulk send, embedded signing, and embedded requesting endpoints.
[signature\_request/bulk\_send\_with\_template](/api/signature-request/bulk-send-with-template)
[signature\_request/create\_embedded](/api/signature-request/create-embedded)
[signature\_request/create\_embedded\_with\_template](/api/signature-request/create-embedded-with-template)
[signature\_request/bulk\_create\_embedded\_with\_template](/api/signature-request/bulk-create-embedded-with-template)
[unclaimed\_draft/create](/api/unclaimed-draft/create)
[unclaimed\_draft/create\_embedded](/api/unclaimed-draft/create-embedded)
[unclaimed\_draft/create\_embedded\_with\_template](/api/unclaimed-draft/create-embedded-with-template)
[unclaimed\_draft/edit\_and\_resend/\{signature\_request\_id}](/api/unclaimed-draft/edit-and-resend) | | Premium | Access to embedded template endpoints. Note that this plan comes with lots of advanced signer fields and signing tools.
[template/create\_embedded\_draft](/api/template/create-embedded-draft)
[template/update\_files/\{template\_id}](/api/template/update-files) | *** ## Rate Limits To maximize stability for everyone, the Dropbox Sign API enforces rate limits on the number of API calls over a specific period of time. Exceeding the rate limits in this section may result in an error with a status code of `429`. By default, you can make up to 100 requests per minute for standard API requests, and 25 requests per minute for higher tier API requests. In test mode, you can do 10 requests per minute. Exceptions can be made for customers with higher volumes. Please [contact us](mailto:apisupport@hellosign.com) for more information. **Higher tier API endpoints:** * [signature\_request/send](/api/signature-request/send) * [signature\_request/send\_with\_template](/api/signature-request/send-with-template) * [signature\_request/bulk\_send\_with\_template](/api/signature-request/bulk-send-with-template) * [signature\_request/create\_embedded](/api/signature-request/create-embedded) * [signature\_request/create\_embedded\_with\_template](/api/signature-request/create-embedded-with-template) * [signature\_request/bulk\_create\_embedded\_with\_template](/api/signature-request/bulk-create-embedded-with-template) * [signature\_request/files](/api/signature-request/files) * [signature\_request/files\_as\_data\_uri](/api/signature-request/files-as-data-uri) * [signature\_request/files\_as\_file\_url](/api/signature-request/files-as-file-url) * [template/files](/api/template/files) * [template/files\_as\_data\_uri](/api/template/files-as-data-uri) * [template/files\_as\_file\_url](/api/template/files-as-file-url) * [template/create\_embedded\_draft](/api/template/create-embedded-draft) * [unclaimed\_draft/create](/api/unclaimed-draft/create) * [unclaimed\_draft/create\_embedded](/api/unclaimed-draft/create-embedded) * [unclaimed\_draft/create\_embedded\_with\_template](/api/unclaimed-draft/create-embedded-with-template) Rate limit information is returned in the HTTP headers of any API request: ```bash maxLines=0 $ curl -i -u '5b2a72b84c3037711d0578e9f93589a38661f093aa4ea48bd8324c16203364eb' https://api.hellosign.com/account HTTP/1.1 200 OK ... X-Ratelimit-Limit: 100 X-Ratelimit-Limit-Remaining: 99 X-Ratelimit-Reset: 1430170900 ... ``` Use these headers to understand how your requests are being limited. | Header Name | Description | | ----------------------------- | ------------------------------------------------------------------ | | `X-Ratelimit-Limit` | The maximum number of requests per hour that you can make. | | `X-Ratelimit-Limit-Remaining` | The number of requests remaining in the current rate limit window. | | `X-Ratelimit-Reset` | The Unix time at which the rate limit will reset to its maximum. | If your application triggers this rate limit, you'll receive the following response: ``` HTTP/1.1 429 Too Many Requests Connection: close Content-Type: application/json ``` ```json maxLines=0 { "error": { "error_msg": "Too many requests. System limits for this type of request are 2000 per hour.", "error_name": "exceeded_rate" } } ``` Use the response headers and message above to limit your requests to the Dropbox Sign API. If you're exceeding your rate limit frequently, you will receive an email notifying you of the overage. It is important to address these notifications, as excessive rate limit abuse will be addressed by blocking the offending account until the situation is resolved. Please [contact us](mailto:apisupport@hellosign.com) if you require a rate limit increase. *** ## API Dashboard