Dropbox (via Apideck)

Access Dropbox through Apideck's File Storage unified API — one of 5 File Storage connectors that share the same method surface. Code you write here ports to SharePoint, Box, Google Drive and 1 other File Storage connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Dropbox plumbing.

Quick facts

Apideck serviceId: dropbox
Unified API: File Storage
Auth type: oauth2
Gotchas: page
Dropbox docs: https://www.dropbox.com/developers
Homepage: https://www.dropbox.com/

At a glance

Implementation difficulty: moderate — Self-Service App Registration + Dropbox Production Approval Required to Connect Users at Scale
Vendor partnership required: no (Dropbox App console) — No contract and no partner programme. Registering an app is free and self-service.
Apideck-managed credentials: available — Temporary shared credentials for trying the connector; going live needs the app owner's own Dropbox app.
Account type required: Any Dropbox account, including a free individual one.
Consumer access level: Any Dropbox user can authorize access to their own account; no administrator role is involved.
Sandbox: not available — Dropbox has no separate test environment.
Costs: No published fee for API access. What an account can do follows its own Dropbox plan.
Rate limits: No published figures. Limits apply per authorized user, or per team for team apps, and Dropbox returns 429 with a Retry-After header.
Authentication: Authorization Code flow.
Webhooks: No webhooks — Dropbox changes are picked up by polling instead.

Important to know:

A Dropbox app starts in Development status. Its 50th connected user starts a two-week clock to obtain Production approval, and Dropbox will not usually review before that point, so applying early does not avoid it. Missing it stops new connections; existing ones keep working.
An app is created with either App folder or Full Dropbox access, and Dropbox does not allow that choice to be changed afterwards. Correcting it means registering a new app, which every already-connected consumer then has to authorize again.
Adding a scope later does not reach consumers who already connected: Dropbox keeps an existing authorization exactly as it was granted and never re-prompts, so each of them has to authorize again before the new permission works.

Facts synced from Apideck's connector metadata API — GET /connector/connectors/dropbox (overview field) is the live, authoritative version.

When to use this skill

Activate this skill when the user explicitly wants to work with Dropbox — for example, "upload a file in Dropbox" or "list a folder in Dropbox". This skill teaches the agent:

Which Apideck unified API covers Dropbox (File Storage)
The correct serviceId to pass on every call (dropbox)
Dropbox-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

File Storage: https://specs.apideck.com/file-storage.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List files in Dropbox
const { data } = await apideck.fileStorage.files.list({
  serviceId: "dropbox",
});

Portable across 5 File Storage connectors

The Apideck File Storage unified API exposes the same methods for every connector in its catalog. Switching from Dropbox to another File Storage connector is a one-string change — no rewrite, no new SDK.

// Today — Dropbox
await apideck.fileStorage.files.list({ serviceId: "dropbox" });

// Tomorrow — same code, different connector
await apideck.fileStorage.files.list({ serviceId: "sharepoint" });
await apideck.fileStorage.files.list({ serviceId: "box" });

This is the compounding advantage of using Apideck over integrating Dropbox directly: code against the unified File Storage API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.