Dropbox APIs for AI Agents
StorageDocument ManagementCollaborationJentic-Generated SpecsOAuth 2.0basic, bearerAgent Ready
Dropbox API Catalog
2 APIs across 2 product groups.
Which Dropbox API should I use?
| I want to... | Use | 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. |
Install Jentic One Beta
Connect the Dropbox APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dropbox APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdropbox.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdropbox.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “store a document in Dropbox and send it for electronic signature”.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
FAQs
Specific to using Dropbox APIs through Jentic.
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.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
