Brushfire
Brushfire is an event ticketing, registration, and virtual event platform used by churches, ministries, conferences, attractions, and large events. Alongside its hosted box office, embeddable event widgets, and mobile check-in apps, Brushfire publishes a documented REST API at api.brushfire.com covering events, ticket types, sections and seats, attendees, orders, the shopping cart and checkout flow, groups, sessions and check-in, promotions and access codes, payment profiles, and webhooks. The API is date-versioned through an api-version request header and authenticated with an App Key requested from developer.brushfire.com.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Brushfire the way a machine reads it — 39 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 — Brushfire scores 34.1/100 (thin), with a separate agent-readiness read of 27/100 (agent aware). 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.
Put this on your own site. The badge is drawn live from Brushfire'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/brushfire/"
title="Brushfire on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/brushfire.svg"
alt="Brushfire Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/brushfire/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/brushfire/"
title="Brushfire on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/brushfire/card.svg"
alt="Brushfire 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 Brushfire
Each block below is one kind of artifact we hold for Brushfire. 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 16
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.
Brushfire AccessCodes API
The AccessCodes API from Brushfire — 3 operation(s) for accesscodes.
Brushfire Accounts API
The Accounts API from Brushfire — 3 operation(s) for accounts.
Brushfire Attendees API
The Attendees API from Brushfire — 18 operation(s) for attendees.
Brushfire Cart API
The Cart API from Brushfire — 11 operation(s) for cart.
Brushfire Clients API
The Clients API from Brushfire — 3 operation(s) for clients.
Brushfire Data API
The Data API from Brushfire — 1 operation(s) for data.
Brushfire Events API
The Events API from Brushfire — 27 operation(s) for events.
Brushfire Exchanges API
The Exchanges API from Brushfire — 2 operation(s) for exchanges.
Brushfire Groups API
The Groups API from Brushfire — 7 operation(s) for groups.
Brushfire Hooks API
The Hooks API from Brushfire — 7 operation(s) for hooks.
Brushfire Lookups API
The Lookups API from Brushfire — 6 operation(s) for lookups.
Brushfire Orders API
The Orders API from Brushfire — 11 operation(s) for orders.
Brushfire PaymentProfiles API
The PaymentProfiles API from Brushfire — 4 operation(s) for paymentprofiles.
Brushfire Promotions API
The Promotions API from Brushfire — 4 operation(s) for promotions.
Brushfire Regions API
The Regions API from Brushfire — 1 operation(s) for regions.
Brushfire Sessions API
The Sessions API from Brushfire — 10 operation(s) for sessions.
Scroll within the panel for all 16 ·
Open Collections 17
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 COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Accounts API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Attendees API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Cart API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Clients API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Data API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Events API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Exchanges API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Groups API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Hooks API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Lookups API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Orders API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Promotions API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Regions API
OPEN COLLECTIONBrushfire API: Version 2025-07-22 AccessCodes Sessions API
OPEN COLLECTIONScroll within the panel for all 17 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Brushfire Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Brushfire Finops
FINOPSSecurity 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.
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 Brushfire — 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 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Operate 1
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/brushfire · machine-readable index on apis.io
This is an independent, third-party profile of Brushfire, 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.