basecamp

name	basecamp
description	Basecamp via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Basecamp's native API. Use when the user wants to call Basecamp (no unified API resource mapping). Routes through Apideck with serviceId "basecamp".
license	Apache-2.0
alwaysApply	false
metadata	{"author":"apideck","version":"1.0.0","serviceId":"basecamp","proxyOnly":true,"unifiedApis":[],"authType":"oauth2","tier":"2","verified":true,"status":"beta"}

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:

1. That Basecamp routes through Apideck's Proxy API, not a unified resource API
2. The correct serviceId to pass on every call (basecamp)
3. How to keep using Basecamp's native request/response shapes while Apideck handles Vault auth

If you need a unified-API surface (one method shape across many vendors), see the connector skills in this catalog whose serviceId is mapped to a unified API.

Auth

• Type: OAuth 2.0
• Managed by: Apideck Vault — Apideck handles the full OAuth dance (authorization code flow, token exchange, refresh). Never ask the user for API keys or tokens directly.
• User setup: Users authorize via the Vault modal. Connection state progresses available → added → authorized → callable.
• Token refresh: automatic. Expired tokens are refreshed transparently on the next API call.

Calling Basecamp via the Proxy API

Send any HTTP request to https://unify.apideck.com/proxy. Apideck looks up the user's stored Basecamp credentials by x-apideck-consumer-id + x-apideck-service-id, injects them on the way out, and returns Basecamp's raw response.

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: basecamp" \
  -H "x-apideck-downstream-url: <target endpoint on Basecamp>" \
  -H "x-apideck-downstream-method: GET"

For POST/PATCH/PUT/DELETE, change x-apideck-downstream-method and pass the body as you would to Basecamp directly. Apideck does not transform the body — it forwards bytes.

See Basecamp's API docs for available endpoints.

See also

• Basecamp gotchas
• Apideck Proxy API reference
• apideck-rest — REST patterns including the Proxy
• apideck-best-practices — Vault, error handling, retries
• apideck-unified-api — when to use unified vs proxy
• Basecamp official docs