Basecamp (via Apideck Proxy)

Access Basecamp through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to Basecamp's native API — you keep using Basecamp's own request and response shapes, while Apideck eliminates per-tenant credential plumbing and gives you a single auth integration shared across every Apideck connector.

Auth-only / proxy-only connector. Apideck does not map Basecamp to a unified-API resource model — your code talks Basecamp's own API directly through the Proxy. You still get Vault credential storage, token refresh, retries, and a consistent request envelope.

Quick facts

• Apideck serviceId: basecamp
• Mode: Proxy-only (no unified API resources)
• Auth type: oauth2
• Status: beta
• Gotchas: page
• Basecamp docs: https://github.com/basecamp/bc3-api
• Homepage: https://basecamp.com

When to use this skill

Activate this skill when the user wants to call Basecamp via Apideck — for example, "call the Basecamp API" or "fetch data from Basecamp". This skill teaches the agent: