sync data and process transactions with the brushfire api
domain: developer.brushfire.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request an API key at developer.brushfire.com/key to get access to Brushfire's REST HTTP API.
Review the full endpoint catalog and schema documentation on the Brushfire developer portal before building an integration.
Use the API for the use cases Brushfire highlights: synchronizing data with existing systems, reserving attendees, and processing transactions.
Pair the REST API with Brushfire's other integration options (e.g. Zapier, Zendesk app) for simpler workflows that don't need a full custom build.
Test against a non-production event before wiring reservation/transaction-processing calls into a live event, since those actions affect real inventory.
Known gotchas
Requesting API access is a gated, key-issuance step rather than instant self-serve signup — plan for a request/approval turnaround.
The API can process transactions and reserve attendees directly, so treat write-capable calls with the same production care as the Brushfire admin UI.
Exact endpoint paths/schemas sit behind the developer portal rather than a fully public reference — verify resource names in the portal itself rather than assuming generic REST conventions.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?