providers/claude/plugin/skills/campfire/SKILL.md
Campfire integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Campfire. Routes through Apideck with serviceId "campfire".
npx skillsauth add apideck-libraries/api-skills campfireInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
campfireActivate 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:
serviceId to pass on every call (campfire)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-restFor the raw OpenAPI spec:
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",
});
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 is a modern accounting platform designed for fast-growing companies with multi-entity and multi-dimensional tracking needs. Very broad Apideck coverage.
| 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 |
updated_at — use Proxyconst { data } = await apideck.accounting.bills.list({
serviceId: "campfire",
filter: { department_id: "dept_marketing" },
});
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.
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.
apideck-connector-coverage — programmatic coverage checksapideck-best-practices — architecture, Vault, pagination, error handlingapideck-node — TypeScript / Node SDK patternsdevelopment
Jira Teams via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Teams's native API. Use when the user wants to call Jira Teams (no unified API resource mapping). Routes through Apideck with serviceId "jira-teams".
development
Jira Service Desk via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Service Desk's native API. Use when the user wants to call Jira Service Desk (no unified API resource mapping). Routes through Apideck with serviceId "jira-service-desk".
development
Jira Data Center via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Data Center's native API. Use when the user wants to call Jira Data Center (no unified API resource mapping). Routes through Apideck with serviceId "jira-data-center".
development
JetBrains YouTrack via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to JetBrains YouTrack's native API. Use when the user wants to call JetBrains YouTrack (no unified API resource mapping). Routes through Apideck with serviceId "jetbrains-youtrack".