Dropbox APIConnect Dropbox without building on its API
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. If you're reading the docs because you need Dropbox to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Dropbox and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
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.
Building on the Dropbox API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Dropbox credentials, and manage tokens and refreshes. | Connect your Dropbox account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Dropbox task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Dropbox work off someone's desk, the build is the slow part.
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.
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. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
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.
Connect Dropbox without the build.
Drop your work email and pick a time. We'll show you Caddi running your Dropbox workflow end to end.