canonical: https://jentic.com/apis/dropbox.com/dropbox-sign-api

# Dropbox Sign API

Jentic publishes the only available OpenAPI specification for Dropbox Sign API, keeping it validated and agent-ready. Dropbox Sign (formerly HelloSign) is a legally binding electronic signature service that lets applications send documents for signature, embed signing flows, manage templates, and handle bulk dispatch. The API exposes 73 endpoints covering signature requests, templates, team and account management, embedded sign and edit URLs, fax, OAuth, and reporting. Authentication accepts either HTTP Basic with an API key or OAuth 2.0 bearer tokens.

## For AI agents

Send documents for e-signature, manage templates, and embed signing flows with Dropbox Sign. Supports bulk dispatch, embedded signatures, and OAuth-scoped agent access.

## Scope

Does not handle file storage, document collaboration, or notarization - use for electronic signature workflows only.

## Capabilities

- Send a document for electronic signature via POST /signature_request/send
- Create reusable templates and dispatch them with POST /signature_request/send_with_template
- Issue embedded signing and template editing URLs via /embedded/sign_url and /embedded/edit_url
- Bulk-dispatch signature requests through /signature_request/bulk_send_with_template
- Manage team membership, API apps, and account settings under /team, /api_app, and /account
- Generate downloadable signed-document files from /signature_request/files
- Retrieve reports on activity and usage through /report

## Use cases

### Sales Contract Dispatch

Send sales contracts and order forms for signature directly from a CRM or deal-room workflow. POST /signature_request/send accepts the document, signers, and field placement, then issues an email request and returns a signature_request_id the agent can poll. Round-trip from draft to fully signed PDF typically takes minutes once signers respond.

Example prompt: POST /signature_request/send with a PDF, two signer emails, and required fields, then poll GET /signature_request/{id} until status is signed and download the file via GET /signature_request/files/{id}

### Embedded Signing in a Web App

Embed a Dropbox Sign signing flow inside a web product so users sign without leaving the app. The agent calls /embedded/sign_url to mint a single-use signing URL after creating a request with embedded=true, then the front-end loads the URL in the Dropbox Sign iframe. This avoids handling document storage and signature legality in your own stack.

Example prompt: Create an embedded signature request via POST /signature_request/create_embedded, then call GET /embedded/sign_url/{signature_id} and return the URL to the front-end

### Bulk Signature Dispatch from a Template

Send the same templated document to hundreds or thousands of recipients in a single bulk operation, useful for HR onboarding waves or compliance attestations. POST /signature_request/bulk_send_with_template accepts a template_id and a CSV-style signer list and creates a bulk_send_job whose status the agent polls via /bulk_send_job/{id}.

Example prompt: POST /signature_request/bulk_send_with_template with template_id and 500 signer rows, then poll GET /bulk_send_job/{bulk_send_job_id} until completed

### Agent-Driven Signature Workflows via Jentic

Wire Dropbox Sign into agent workflows that draft, dispatch, and reconcile signed documents. Through Jentic the agent searches by intent, loads the schema for /signature_request/send, and executes without scraping HelloSign's reference, which keeps the integration loop short and keeps API keys out of agent context.

Example prompt: Search Jentic for 'send a document for signature', load the Dropbox Sign /signature_request/send schema, and execute with signer details supplied by the parent workflow

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /signature_request/send | Send a document for signature |
| GET | /signature_request/{signature_request_id} | Get a signature request |
| POST | /signature_request/send_with_template | Send a signature request from a template |
| GET | /embedded/sign_url/{signature_id} | Get an embedded sign URL |
| POST | /embedded/edit_url/{template_id} | Get an embedded template edit URL |
| GET | /bulk_send_job/{bulk_send_job_id} | Get bulk send job status |
| GET | /account | Get account details |

## Key resources

- **Signature Request** — Send, retrieve, cancel, and download signed documents under /signature_request
- **Template** — Create and manage reusable signing templates under /template
- **Embedded** — Mint embedded signing and template-edit URLs under /embedded
- **Bulk Send Job** — Track multi-recipient dispatches under /bulk_send_job
- **Account & Team** — Manage user, team, and API app settings under /account, /team, and /api_app

## Why Jentic

- **Setup:** Wiring the Dropbox Sign API by hand means choosing between its HTTP basic API-key auth and OAuth bearer tokens and building each signature-request call against the HelloSign v3 host yourself. Through Jentic you install once, import Dropbox Sign from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Dropbox Sign identifies a signature request or template in the request body, so you limit the agent to the operations it needs, such as sending a request from a template or checking signature status. You choose which operations are allowed, so bulk send jobs are not included unless you add them.
- **Credential handling:** Your Dropbox Sign API key or OAuth bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a document for signature' or 'check signature status', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the HelloSign reference.

## Related APIs

- **PandaDoc API** — Document automation and esignature platform with stronger CPQ and proposal templating than Dropbox Sign
- **Rebrandly API** — Branded short links for tracking signature request emails
- **Shopify Admin API** — Trigger contract signing flows from commerce events like high-value orders

## FAQ

### Why is there no official OpenAPI spec for Dropbox Sign API?

Dropbox does not publish an OpenAPI specification for Dropbox Sign that matches the live v3 surface. Jentic generates and maintains this spec so that AI agents and developers can call Dropbox Sign API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Dropbox Sign API use?

The API accepts HTTP Basic with an API key as the username, or OAuth 2.0 bearer tokens for end-user-scoped access. Through Jentic the credential is stored in the vault and injected at execution, so it never enters the agent prompt.

### Can I send a document for signature with the Dropbox Sign API?

Yes. POST /signature_request/send accepts the document, signers, and field placement and returns a signature_request_id you can poll via GET /signature_request/{signature_request_id}.

### What are the rate limits for the Dropbox Sign API?

Limits are not declared in the OpenAPI spec. Dropbox Sign documents account-level quotas in the dashboard; have your agent retry on HTTP 429 with exponential backoff.

### How do I run a bulk signature dispatch through Jentic?

Search Jentic for 'bulk send signature requests', load the schema for POST /signature_request/bulk_send_with_template, and execute with a template_id and signer list. Then poll GET /bulk_send_job/{bulk_send_job_id} for completion. Install with pip install jentic.

### Can I embed signing inside my own application?

Yes. Create an embedded request, then call GET /embedded/sign_url/{signature_id} to mint a single-use signing URL that loads in the Dropbox Sign iframe.

### Can I limit what my agent is allowed to do with the Dropbox Sign API?

Yes. Because you self-host Jentic One, your own rules decide which Dropbox Sign operations and credentials the agent may use, so you can allow only the endpoints a task needs, such as sending a request from a template or checking signature status via GET /signature_request/{signature_request_id}. Since the request or template is identified in the request body, the agent can act only on the operations you permit. Broader actions like bulk dispatch through POST /signature_request/bulk_send_with_template stay off unless you explicitly add them.