domain: breezechms.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an API key from the church's Breeze account under Extensions > API, per the Breeze API Reference at apidocs.breezesoftware.com.
Include the API key on every request (as documented — parameter or header) since Breeze uses long-lived per-account keys rather than OAuth apps.
List or filter people via the people list endpoint, using filter_json for tag- or field-based filtering.
Create or update a person via the person endpoints, supplying core fields (name, email, phone) plus any org-specific custom profile fields.
List events with a start/end date range via the events endpoint; be aware Breeze notes this data can be cached and lag up to ~15 minutes behind the live site.
Known gotchas
There's no OAuth app model — every call is authorized by a single long-lived API key tied to one church's account, so treat it as a sensitive secret.
Events data may be stale by design (cache lag up to ~15 min) — don't rely on it to confirm real-time check-ins.
Custom profile fields vary per church; fetch that org's field definitions rather than hardcoding field names.
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?