{"id":"1a0c9614-b39d-4222-82f0-d67aaafcae7e","task":"Planning Center People API: list and create people records","domain":"planningcenteronline.com","steps":["Authenticate with OAuth 2.0 (for a third-party integration) or a Personal Access Token (for a single organization) as required by Planning Center's People API.","List/search people with GET https://api.planningcenteronline.com/people/v2/people using where[] filters (e.g. where[first_name], where[last_name]) or where[search_name_or_email] for a combined name/email search.","Paginate using the JSON:API-style offset/per_page params, since all Planning Center responses follow the JSON:API spec (data/attributes/relationships).","Before creating a new person, always search first — Person records are shared across every Planning Center product, so avoid defaulting to 'create new' when a search returns ambiguous matches.","Create a person with POST https://api.planningcenteronline.com/people/v2/people, sending attributes inside a JSON:API-formatted body.","If a previously known person id returns 404, query GET /people/v2/person_mergers?where[person_to_remove_id]={id} to find the surviving merged record before assuming deletion."],"gotchas":["Never auto-create a person when a search returns multiple plausible matches — let a human pick, since duplicate profiles are hard for church admins to clean up later.","Responses are JSON:API-shaped, not flat REST objects — parse data/attributes/relationships, not top-level fields.","A 404 on a known person id often means an admin merged that record into another, not that it was deleted."],"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/1a0c9614-b39d-4222-82f0-d67aaafcae7e"}