Read ChurchSuite module data (e.g. address book contacts) via the Core API v2 with OAuth2
domain: developer.churchsuite.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an OAuth2 application in your ChurchSuite account's developer settings
Direct users to youraccount.churchsuite.com/oauth to authorize the application and obtain an access token
Call Core API v2 read endpoints (e.g. address book / people) documented at developer.churchsuite.com using the access token
Check the current module reference before assuming a write endpoint exists, since write support is being added incrementally
Known gotchas
The legacy v1 API is deprecated in favor of v2; ChurchSuite has stated it anticipates turning v1 off in 2027, so target v2 for new integrations
Core API v2 currently supports read endpoints for all modules except Rotas, with write support still rolling out module by module — do not assume full CRUD is available everywhere
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?