Planning Center Check-Ins API: pull attendance data
domain: planningcenteronline.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with OAuth 2.0 or a Personal Access Token with Check-Ins access.
List events and their event_times with GET /check-ins/v2/events (and nested event_times) to identify which service/gathering you're pulling attendance for.
Pull attendance records with GET /check-ins/v2/check_ins, optionally scoped to a specific event via nested routes; each record represents a single person's single check-in, not a person-level summary.
Include the related person with include=person to resolve each check-in back to a People record for reporting.
Apply date-range filters (e.g. where[created_at]) to keep result sets manageable, consistent with Planning Center's general guidance against unbounded queries.
Known gotchas
A check-in record is per-visit — expect many repeat entries for regular attenders across services, not one row per person.
Filter by event/event_time to avoid mixing datasets from unrelated gatherings when computing attendance totals.
Exact endpoint nesting/casing should be confirmed against the live Check-Ins docs, since resource naming differs from People/Services.
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?