TouchPoint Software API: read and write church management data
domain: touchpointsoftware.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Recognize TouchPoint, like Rock RMS, is deployed per-church — API calls target that specific church's own TouchPoint domain, not a shared host.
Authenticate using a Personal Access Token (per docs.touchpointsoftware.com's PersonalAccessTokens guide) or the documented external-application token flow.
For structured read queries (people, groups, involvements, attendance), use the OData API with standard OData filter/query syntax.
For pushing data into TouchPoint (e.g. recording attendance or check-ins from an external system), use the Push Post API.
Confirm exact endpoint paths and fields for that specific TouchPoint version against its built-in Swagger API documentation before building.
Known gotchas
There is no shared global base URL — every integration must target the specific church's own TouchPoint domain.
OData (read) and Push Post (write) are distinct API surfaces with separate auth/usage patterns; don't assume one covers both directions.
Endpoint availability and field names can differ by TouchPoint version — verify against that instance's live Swagger docs, not a cached spec.
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?