Campfire

At a Glance

Difficulty

⚡MODERATEAPI Key authentication — the consumer creates a dedicated API user and key in Campfire

Authentication

API KeyAPI Key — the consumer supplies a token sent as an Authorization: Token <key> header. Not OAuth; the key is static with no documented expiry.

Webhooks

No webhooks — neither native nor virtual; poll for changes. Campfire's own API offers webhook subscriptions, but this connector does not use them.

Partnership Required

No(Not required — the Campfire Partner Program is a commercial referral programme, unrelated to API access.)

Partnership Application

Developer Portal↗

Apideck Credentials

Not available(Not available — each consumer supplies their own Campfire API key.)

Costs

No public price list — Campfire pricing is quote-based and no free tier is documented. No separate fee for API access is documented either.

Sandbox Availability

Available(On request — Campfire has publicly said it provisions evaluation sandboxes; there is no documented self-service signup, so ask Campfire.)

Account Type Required

Campfire account (any plan)

Consumer Access Level

Admin role on a dedicated API user (full read and write); clerk or view only for narrower integrations.

Rate Limits

5 requests/second per API user, shared across all endpoints; exceeding it returns 429 with a Retry-After header.

Responsibility matrix

Environments

Single environment

Campfire declares one API server, so testing and production share the same credential shape — one API key, whichever Campfire account you point it at.

Testing

Whether you test against an evaluation sandbox Campfire provisions for you or a Campfire account you already control, the credential is the same kind of API key — there is no separate development key. Both hold live data, so treat anything the integration writes as production data.