Integrate the Dropbox API.Caddi writes and runs the integration for you.
Dropbox has a REST API. Self-serve for any developer; apps in development status can link only a limited number of users (50) until Dropbox approves production status.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
The connection is a project before it does anything.
Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. Dropbox enforces per-authorization rate limits (HTTP 429 with Retry-After) but explicitly does not publish exact numbers.
Register an app, store Dropbox credentials, refresh tokens and code around the rate limits.
Connect your Dropbox account once. Caddi holds the connection.
The job doesn't stop at Dropbox.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Dropbox API only reaches Dropbox.
Each extra system is another API, another set of credentials, another integration to own.
One automation runs across every tool the job touches, each through its API.
Someone has to own the code.
API versions change, fields get added and your process moves.
A developer patches and redeploys the integration each time.
The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.
What the Dropbox API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0
- Who can get access
- Self-serve for any developer; apps in development status can link only a limited number of users (50) until Dropbox approves production status.
- What it covers
- Files and folders, sharing, users/accounts, and Dropbox Business team administration.
- Limits
- Dropbox enforces per-authorization rate limits (HTTP 429 with Retry-After) but explicitly does not publish exact numbers.
Official docs: dropbox.com. Checked September 2026. Vendors change access terms, so confirm with Dropbox before you build.
When to build the Dropbox integration in-house
When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Dropbox work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the Dropbox API for
Classify-and-file inbound docs
Caddi reads new files in a watched Dropbox folder, classifies them, applies the firm's naming convention, and moves them to the right destination.
Signed-doc archive
When a signed envelope lands in Dropbox, Caddi pulls the data, updates the CRM, and files the document with metadata.
Cross-cloud sync
Caddi mirrors approved documents from Dropbox to SharePoint or Box with the right metadata applied at the destination.
Everything Caddi does with Dropbox.
Dropbox API questions
Does Dropbox have an API?
Yes. Dropbox has a REST API, authenticated with OAuth 2.0. The official documentation is at https://www.dropbox.com/developers/documentation/http/documentation.
How do I get access to the Dropbox API?
Self-serve for any developer; apps in development status can link only a limited number of users (50) until Dropbox approves production status.
Does the Dropbox API have rate limits?
Dropbox enforces per-authorization rate limits (HTTP 429 with Retry-After) but explicitly does not publish exact numbers.
Can I connect Dropbox to my other tools without writing code against its API?
Yes. With Caddi you show the Dropbox task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Dropbox and the other tools the job touches. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.
Do I need a developer to automate Dropbox with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Dropbox is reviewed before it runs in production, and every run is logged.