[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Planning Center API

> Every Planning Center endpoint on Cotlet: inputs, JSON Schema, cURL, Python and Node.js examples and an example response for each call.

Source: https://cotlet.dev/docs/api/planning-center

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

12 endpoints for Planning Center, each at its own method and path, called with your API key. Open an endpoint for its inputs, examples and response.

- Base URL: `https://cotlet.dev/api/v1/planning-center`
- Connects with: Your own Planning Center login. What the agent can do follows your permissions in each product: scheduling needs a team leader role in Services, notes need access to the note category in People.
- Integration page: https://cotlet.dev/integrations/planning-center-api-mcp-server

## Read

Return data and change nothing in the account.

| Endpoint | Description |
|---|---|
| [`GET /peoples/search`](https://cotlet.dev/docs/api/planning-center/search_people.md) | People profiles that match a name or email. |
| [`GET /persons/{person_id}`](https://cotlet.dev/docs/api/planning-center/get_person.md) | One People profile with contact details and the notes you can see. |
| [`GET /service-plans`](https://cotlet.dev/docs/api/planning-center/list_service_plans.md) | Services plans of a service type in a date range, in date order. |
| [`GET /plans/{plan_id}/team`](https://cotlet.dev/docs/api/planning-center/get_plan_team.md) | Scheduled volunteers of a plan with position, status and whether their email is still waiting. |
| [`GET /my-schedules`](https://cotlet.dev/docs/api/planning-center/list_my_schedule.md) | Your own pending and confirmed requests, as My Schedule shows them. |
| [`GET /workflow-cards`](https://cotlet.dev/docs/api/planning-center/list_workflow_cards.md) | Cards of a People workflow that are ready or snoozed, with person, step and assignee. |
| [`GET /first-timers`](https://cotlet.dev/docs/api/planning-center/list_first_timers.md) | People whose check-in to an event was their first, in a date range. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Endpoint | Description |
|---|---|
| [`POST /plans/{plan_id}/scheduling-emails`](https://cotlet.dev/docs/api/planning-center/send_scheduling_emails.md) (Confirm) | Send the scheduling emails that are still waiting on a plan, for one team, one person or everyone. |
| [`POST /plans/{plan_id}/schedule-request/replies`](https://cotlet.dev/docs/api/planning-center/respond_to_schedule_request.md) (Confirm) | Accept or decline your own pending request for a plan, as you. |
| [`POST /cards/{card_id}/workflow-step/complete`](https://cotlet.dev/docs/api/planning-center/complete_workflow_step.md) (Confirm) | Complete the current step of a workflow card and move it to the next step. |
| [`POST /cards/{card_id}/workflow-card/snooze`](https://cotlet.dev/docs/api/planning-center/snooze_workflow_card.md) | Hide a workflow card from your list for a duration. |
| [`POST /persons/{person_id}/note`](https://cotlet.dev/docs/api/planning-center/add_person_note.md) (Confirm) | Add a note to a person's profile in a note category. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.