Dropbox APIs for AI Agents
StorageDocument ManagementCollaborationJentic-Generated DocumentsOAuth 2.0Basic authBearer tokenAgent Ready
For Agents
APIs2 in catalogue
Endpoints151 indexed
AuthOAuth 2.0 / Basic auth / Bearer token
ProvenanceJentic-generated documents
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.
Dropbox pairs cloud file storage with a native electronic signature service under one brand, so an agent can hold a document and get it legally signed without moving it to a separate provider. The storage API focuses on file operations and sharing, while Dropbox Sign focuses on signature requests, templates, and embedded signing.
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
Credentials: No single credential covers both APIs: the Dropbox API v2 uses OAuth 2.0, while the Dropbox Sign API uses an HTTP Basic API key or an OAuth 2.0 bearer token, so each API is authorized separately.
All 2 Dropbox OpenAPI documents are Jentic-generated and indexed by Jentic, kept validated and agent-ready.
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.
Dropbox API Catalog
2 APIs across 2 product groups.
Which Dropbox API should I use?
| I want to... | Use |
|---|---|
| Store, sync, search, and share files or folders | Dropbox API v2 |
| Send a document for legally binding electronic signature | Dropbox Sign API |
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”.
What AI Agents Can Do with Dropbox
Each workflow spans multiple Dropbox APIs. Jentic routes each operation to the right API automatically.
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
APIs used
Dropbox API v2 + Dropbox Sign API
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
APIs used
Dropbox Sign API + Dropbox API v2
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
APIs used
Dropbox Sign API + Dropbox API v2
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.
Intent-based discovery
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.
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.
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.
If you need a different Storage vendor
All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.
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.