Campfire
Campfire is an AI-native ERP built for high-growth startups and mid-market finance teams outgrowing QuickBooks or Xero, or replacing NetSuite and Sage Intacct. It automates core accounting work — general ledger, bank reconciliation, accounts payable and receivable, revenue recognition, close management, and financial reporting — with an AI assistant (Ember). Campfire ships developer-first REST APIs (188 paths / 362 operations across Cash Management, Core Accounting, Accounts Payable/Receivable, Revenue Recognition, Financial Statements, and Integrations), an official hosted Model Context Protocol (MCP) server, and outbound webhooks. Founded 2023; backed by Accel, Ribbit Capital, Foundation Capital, Capital49, and Y Combinator.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Campfire the way a machine reads it — 31 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Campfire scores 50.3/100 (developing), with a separate agent-readiness read of 54/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Campfire's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/campfire/"
title="Campfire on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/campfire.svg"
alt="Campfire Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/campfire/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/campfire/"
title="Campfire on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/campfire/card.svg"
alt="Campfire Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Campfire
Each block below is one kind of artifact we hold for Campfire. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Campfire Accounts Payable API
Operations related to billing and the AP subledger.
Campfire Accounts Receivable API
Operations related to invoicing and the AR subledger
Campfire Bank Reconciliation API
The Bank Reconciliation API from Campfire — 6 operation(s) for bank reconciliation.
Campfire Cash Management API
Operations related to accounts, transactions, and other bank-related data.
Campfire coa API
The coa API from Campfire — 1 operation(s) for coa.
Campfire Company Objects API
The Company Objects API from Campfire — 21 operation(s) for company objects.
Campfire Core Accounting API
Operations related to core accounting data, such as the chart of accounts, entity management, and the general ledger.
Campfire Custom Fields API
The Custom Fields API from Campfire — 1 operation(s) for custom fields.
Campfire Financial Statements API
Operations related to financial statement generation and data aggregation.
Campfire Integrations API
The Integrations API from Campfire — 3 operation(s) for integrations.
Campfire Revenue Recognition API
Operations related to revenue recognition, contract management, and contract data aggregation.
Campfire Settings API
Operations related to system and accounting settings configuration.
Scroll within the panel for all 12 ·
Open Collections 13
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONCampfire Developer APIs Accounts Payable API
OPEN COLLECTIONCampfire Developer APIs Accounts Payable Cash Management API
OPEN COLLECTIONCampfire Developer APIs Accounts Payable coa API
OPEN COLLECTIONCampfire Developer APIs Accounts Payable Company Objects API
OPEN COLLECTIONCampfire Developer APIs Accounts Payable Core Accounting API
OPEN COLLECTIONCampfire Developer APIs Accounts Payable Custom Fields API
OPEN COLLECTIONCampfire Developer APIs Accounts Payable Integrations API
OPEN COLLECTIONCampfire Developer APIs Accounts Payable Settings API
OPEN COLLECTIONScroll within the panel for all 13 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Campfire
Campfire exposes an official hosted (remote HTTP) MCP server that maps 12 tools directly onto its accounting, company-data, financial-reporting, and revenue/budget API endpoints...
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Campfire Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Campfire — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/campfire · machine-readable index on apis.io
This is an independent, third-party profile of Campfire, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.