canonical: https://jentic.com/apis/dropbox.com

# Dropbox APIs

Dropbox provides cloud file storage and electronic signature services through two APIs. The Dropbox API v2 handles file upload, download, folder organization, sharing links, and revision history across cloud storage. The Dropbox Sign API (formerly HelloSign) sends documents for legally binding electronic signature, manages reusable templates, embeds signing flows, and dispatches bulk signature requests. Together they cover storing a document and getting it signed.

## For AI agents

An agent can store, retrieve, search, and share files in Dropbox cloud storage, then send those same documents for electronic signature, track signing status, and download the completed signed PDF. It can manage folders, revision history, templates, and bulk signature dispatch across both APIs.

## Scope

Use for: Storing, sharing, and syncing files in Dropbox cloud storage and sending documents for electronic signature through Dropbox Sign

Not supported:
- object storage buckets
- notarization
- document editing
- long-term retention policies
- legal holds

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Dropbox API v2 | storage | 78 | Upload, download, and organize files in Dropbox cloud storage. |
| Dropbox Sign API | productivity | 73 | Send documents for e-signature, manage templates, and embed signing flows with Dropbox Sign. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Store, sync, search, and share files or folders | dropbox-api-v2 | The Dropbox API v2 handles file upload and download, folder organization, shared links, and revision history in cloud storage. |
| Send a document for legally binding electronic signature | dropbox-sign-api | The Dropbox Sign API sends signature requests, manages templates, embeds signing flows, and dispatches bulk requests. |

## Cross-API use cases

### Store a contract, then send it for signature

An agent uploads a drafted contract to a Dropbox folder, generates a shared link for internal review, then sends the same document for electronic signature through Dropbox Sign and polls until it is signed. The signed PDF is written back to Dropbox for retention.

Example prompt: Upload contract.pdf to /contracts using /2/files/upload, then POST /signature_request/send with the signer emails and poll GET /signature_request/{id} until status is signed

### Archive signed documents back to cloud storage

After a signature request completes in Dropbox Sign, an agent downloads the finished signed PDF and files it into a dated Dropbox folder, then creates an expiring shared link so the counterparty can retrieve their copy.

Example prompt: Fetch the signed file via GET /signature_request/files/{id}, upload it to /signed/2026 with /2/files/upload, then create an expiring link with /2/sharing/create_shared_link_with_settings

### Bulk onboarding: distribute and collect signed forms

An agent dispatches an onboarding document to hundreds of recipients from a Dropbox Sign template, tracks the bulk job to completion, then stores each returned signed form in a per-recipient Dropbox folder for the records team.

Example prompt: POST /signature_request/bulk_send_with_template with a template_id and signer rows, poll GET /bulk_send_job/{id}, then create folders with /2/files/create_folder_v2 and upload each signed file

## Why Jentic

- **Setup:** Wiring Dropbox by hand means running the OAuth 2.0 flow for file storage and separately handling the Dropbox Sign API key or bearer token against the HelloSign v3 host. Through Jentic you install once, add each Dropbox API from the Jentic directory, store the credentials once, and your agent calls both.
- **Permission scoping:** The Dropbox API v2 governs access through OAuth scopes like files.content.read and sharing.write, and Dropbox Sign identifies each request or template in the body. Your own Jentic One rules limit the agent to the operations you allow, so a destructive delete or a bulk send job is not included unless you add it.
- **Credential handling:** Your Dropbox OAuth secrets and your Dropbox Sign API key are stored once, encrypted, by your own Jentic One instance and exchanged for scoped access at execution time. Raw secrets and tokens never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search the Jentic directory by intent such as 'upload a file to Dropbox' or 'send a document for signature', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint across either API without browsing the reference docs.

## Related vendors

- **Box** — Cloud content management platform used as an alternative to Dropbox file storage, with governance features like retention and legal holds.
- **PandaDoc** — Document automation and electronic signature platform that overlaps with Dropbox Sign, with stronger proposal and pricing templating.
- **Google** — Google Drive offers file storage and collaboration as an alternative to Dropbox for teams on Google Workspace.

## FAQ

### What can an agent do across the Dropbox APIs?

An agent can store, search, and share files in Dropbox cloud storage through the Dropbox API v2, and send those documents for legally binding electronic signature through the Dropbox Sign API. A common end-to-end flow is uploading a document, sending it for signature, and filing the signed PDF back into a folder.

### Do the two Dropbox APIs share one set of credentials?

No. The Dropbox API v2 authenticates with OAuth 2.0, while the Dropbox Sign API accepts an HTTP Basic API key or an OAuth 2.0 bearer token. You authorize each API separately, and through Jentic each credential is stored and scoped independently.

### Is Dropbox Sign the same product as HelloSign?

Yes. Dropbox Sign is the current name for the service formerly called HelloSign, and its API still runs against the HelloSign v3 host. It handles signature requests, templates, embedded signing, and bulk dispatch, and it is a separate API from Dropbox file storage.

### Can I run a full store-then-sign workflow with these APIs?

Yes. Upload a document with the Dropbox API v2, send it for signature with the Dropbox Sign API, poll until the signature request is complete, then download the signed file and store it back in Dropbox. Each step maps to a distinct operation in one of the two APIs.

### Why are these Dropbox APIs available through Jentic when Dropbox has no OpenAPI spec?

Dropbox does not publish OpenAPI specifications for these services. Jentic generates and maintains a validated spec for each API so agents and developers can call them through structured tooling, and keeps both specs current against the live APIs.

### What is the difference between Dropbox storage sharing and Dropbox Sign?

A Dropbox shared link distributes a file for viewing or editing and carries no legal weight. A Dropbox Sign request collects a legally binding electronic signature on a document. Use shared links for distribution and Dropbox Sign when a signature is required.