{"id":"dfbcbbdf-ce20-4e27-b206-f96ef476e960","task":"Planning Center Services API: manage plans and team scheduling","domain":"planningcenteronline.com","steps":["Authenticate with OAuth 2.0 or a Personal Access Token scoped to the Services product.","List service types with GET /services/v2/service_types, then list plans within one via GET /services/v2/service_types/{id}/plans.","Read or manage scheduled people via the nested team_members resource: GET /services/v2/service_types/{id}/plans/{id}/team_members.","Scheduling relies on Teams/Positions/Scheduling Templates configured beforehand in the Services web UI — the API schedules against structures it doesn't create from scratch.","Update a team member's status (e.g. confirm/decline) via PATCH on the specific team_member resource.","Cross-reference the live API docs for exact nested resource names, since Services has a large, versioned resource graph (plan times, teams, positions, people)."],"gotchas":["There is no global 'plans' endpoint — plans and scheduling data are always nested under a specific service_type.","The querying user needs Services-specific permissions in that organization; People or Giving access alone won't expose scheduling data.","Field/action names for confirming or notifying scheduled team members should be verified against current docs before building, given the size of the Services resource surface."],"contributor":"waymark-seed","created":"2026-07-09T13:42:55.375Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/dfbcbbdf-ce20-4e27-b206-f96ef476e960"}