OneDrive (via Apideck)

Access OneDrive 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, Dropbox 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 OneDrive plumbing.

Quick facts

• Apideck serviceId: onedrive
• Unified API: File Storage
• Auth type: oauth2
• OneDrive docs: https://learn.microsoft.com/onedrive/developer/
• Homepage: https://onedrive.live.com/

When to use this skill

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

1. Which Apideck unified API covers OneDrive (File Storage)
2. The correct serviceId to pass on every call (onedrive)
3. OneDrive-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 OneDrive
const { data } = await apideck.fileStorage.files.list({
  serviceId: "onedrive",
});

Portable across 5 File Storage connectors

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

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

// 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 OneDrive 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.

OneDrive via Apideck File Storage

OneDrive (Microsoft personal + business) is accessed via Microsoft Graph, same as SharePoint. Apideck normalizes the Drive/File/Folder surface.

Entity mapping

Coverage highlights

• ✅ CRUD on files and folders
• ✅ Upload via resumable sessions (required for large files)
• ✅ Download file content
• ✅ Shared links
• ❌ Delta queries (change tracking) — use Proxy with Graph /delta

Auth

• Type: OAuth 2.0 (Microsoft identity platform), managed by Apideck Vault
• Personal vs. Work: both account types work. Personal accounts don't need admin consent; corporate tenants often do for Graph scopes.
• User binding: each connection is bound to one user's OneDrive (unlike SharePoint which exposes site-wide drives).

Example: list files in root

const { data } = await apideck.fileStorage.files.list({
  serviceId: "onedrive",
});

Escape hatch: Proxy API

When an endpoint isn't covered by the File Storage unified API, use Apideck's Proxy to call OneDrive directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on OneDrive'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: onedrive" \
  -H "x-apideck-downstream-url: <target endpoint on OneDrive>" \
  -H "x-apideck-downstream-method: GET"

See OneDrive's API docs for available endpoints.

Sibling connectors

Other File Storage connectors that share this unified API surface (same method signatures, just change serviceId):

sharepoint, box, dropbox, google-drive.

See also

• File Storage OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• OneDrive official docs