campfire
Campfire (via Apideck)
Access Campfire through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Access Financials, Acumatica, banqUP and 30 other Accounting connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Campfire plumbing.
Beta connector. Campfire is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
Quick facts
- Apideck serviceId:
campfire - Unified API: Accounting
- Auth type: apiKey
- Status: beta
- Apideck setup guide: Connection guide
- Gotchas: page
- Campfire docs: https://www.campfire.com
- Homepage: https://campfire.ai/
When to use this skill
Activate this skill when the user explicitly wants to work with Campfire — for example, "create an invoice in Campfire" or "reconcile payments in Campfire". This skill teaches the agent:
- Which Apideck unified API covers Campfire (Accounting)
- The correct
serviceIdto pass on every call (campfire) - Campfire-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, orapideck-rest
For the raw OpenAPI spec:
- Accounting: https://specs.apideck.com/accounting.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 invoices in Campfire
const { data } = await apideck.accounting.invoices.list({
serviceId: "campfire",
});
Portable across 34 Accounting connectors
The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Campfire to another Accounting connector is a one-string change — no rewrite, no new SDK.
// Today — Campfire
await apideck.accounting.invoices.list({ serviceId: "campfire" });
// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "acumatica" });
This is the compounding advantage of using Apideck over integrating Campfire directly: code against the unified Accounting API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
Campfire via Apideck Accounting
Campfire is a modern accounting platform designed for fast-growing companies with multi-entity and multi-dimensional tracking needs. Very broad Apideck coverage.
Entity mapping
| Campfire entity | Apideck Accounting resource |
|---|---|
| Invoice | invoices |
| Bill | bills |
| Bill Payment | bill-payments |
| Credit Note | credit-notes |
| Payment | payments |
| Journal Entry | journal-entries |
| Account | ledger-accounts |
| Customer | customers |
| Supplier | suppliers |
| Item | invoice-items |
| Department | departments |
| Subsidiary | subsidiaries |
| Tracking Category | tracking-categories |
| Bank Feed Account | bank-feed-accounts |
| Bank Feed Statement | bank-feed-statements |
| Company Info | company-info |
| P&L, Balance Sheet | profit-and-loss, balance-sheet |
Coverage highlights
- ✅ Full CRUD on invoices, bills, payments (incl. bill payments)
- ✅ Credit notes
- ✅ Journal entries
- ✅ Departments, subsidiaries, tracking categories (deep multi-dim support)
- ✅ Bank feeds
- ✅ Financial reports (P&L, Balance Sheet)
- ⚠️ Revenue recognition — not in unified; use Proxy
- ❌ Audit trail detail beyond
updated_at— use Proxy
Auth notes
- Type: API key, managed by Apideck Vault
- Organization binding: one Campfire organization per connection.
- Multi-entity: subsidiaries exposed as a first-class resource; scale to dozens of entities per org.
Example: list bills with department filter
const { data } = await apideck.accounting.bills.list({
serviceId: "campfire",
filter: { department_id: "dept_marketing" },
});
Escape hatch: Proxy API
When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Campfire directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Campfire'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: campfire" \
-H "x-apideck-downstream-url: <target endpoint on Campfire>" \
-H "x-apideck-downstream-method: GET"
See Campfire's API docs for available endpoints.
Sibling connectors
Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):
access-financials (beta), acumatica (beta), banqup (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, exact-online-nl (beta), and 25 more.
See also
- Apideck connection guide for Campfire
- Accounting OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- Campfire official docs
More from apideck-libraries/api-skills
apideck-connector-coverage
Check Apideck connector API coverage before building integrations. Use when determining which operations a connector supports, comparing connector capabilities, or diagnosing why an API call fails with a specific connector. Teaches agents to query the Connector API for real-time coverage data.
18apideck-best-practices
Best practices for building Apideck integrations. Covers authentication patterns, pagination, error handling, connection management with Vault, webhook setup, and common pitfalls. Use when designing or reviewing any Apideck integration regardless of language.
18apideck-rest
Apideck Unified REST API reference for any language. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors using direct HTTP calls. Covers authentication headers, CRUD operations, cursor-based pagination, filtering, sorting, error handling, rate limiting, pass-through parameters, and webhooks. Language-agnostic — works with curl, fetch, axios, httpx, or any HTTP client.
16apideck-portman
API contract testing with Portman by Apideck. Use when generating Postman collections from OpenAPI specs, writing contract tests, variation tests, integration tests, fuzz testing, or setting up CI/CD API test pipelines. Portman converts OpenAPI 3.x specs into Postman collections with auto-generated test suites.
14apideck-node
Apideck Unified API integration patterns for TypeScript and Node.js. Use when building integrations with accounting software (QuickBooks, Xero, NetSuite), CRMs (Salesforce, HubSpot, Pipedrive), HRIS platforms (Workday, BambooHR), file storage (Google Drive, Dropbox, Box), ATS systems (Greenhouse, Lever), e-commerce, or any of Apideck's 200+ connectors. Covers the @apideck/unify SDK, authentication, CRUD operations, pagination, filtering, webhooks, and Vault connection management.
14apideck-codegen
Generate typed API clients from Apideck OpenAPI specs using code generators. Use when the user wants to generate custom SDK clients, typed models, API stubs, or server scaffolding from Apideck's published OpenAPI specifications. Covers openapi-generator, Speakeasy, and Postman import workflows.
14