Dropbox integration via Apideck's File Storage unified API — same methods work across every connector in File Storage, switch by changing `serviceId`. Use when the user wants to read, write, upload, or search files, folders, and drives in Dropbox. Routes through Apideck with serviceId "dropbox".
77
73%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./connectors/dropbox/SKILL.mdAccess 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.
dropboxActivate 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:
serviceId to pass on every call (dropbox)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-restFor the raw OpenAPI spec:
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",
});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.
Dropbox is a popular consumer + team file sync product. Apideck covers file, folder, and upload-session operations.
| Dropbox concept | Apideck File Storage resource |
|---|---|
| File | files |
| Folder | folders |
| Upload session | upload-sessions |
| Shared link | not yet exposed — use Proxy |
/sharing/create_shared_link_with_settings for nowteam_member_id context.const { data } = await apideck.fileStorage.files.create({
serviceId: "dropbox",
file: { name: "notes.txt", parent_folder_id: "/" },
});When an endpoint isn't covered by the File Storage unified API, use Apideck's Proxy to call Dropbox directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Dropbox's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: dropbox" \
-H "x-apideck-downstream-url: <target endpoint on Dropbox>" \
-H "x-apideck-downstream-method: GET"See Dropbox's API docs for available endpoints.
Other File Storage connectors that share this unified API surface (same method signatures, just change serviceId):
sharepoint, box, google-drive, onedrive.
apideck-connector-coverage — programmatic coverage checksapideck-best-practices — architecture, Vault, pagination, error handlingapideck-node — TypeScript / Node SDK patterns9e04d86
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.