Planning Center · Rate Limits

Planning Center Rate Limits

Planning Center enforces a documented rate limit of 100 requests per 20 seconds per authenticated user, applied across all products under https://api.planningcenteronline.com. Requests that page with a high offset (above 30,000) are subject to a stricter limit of 75 requests per 20 seconds. Every response returns headers describing the current window, and Planning Center notes that limits can be adjusted dynamically without notice, so clients should read the headers rather than hardcode the numbers. Exceeding the limit returns HTTP 429 with a Retry-After header.

Planning Center Rate Limits is the machine-readable rate-limit profile for Planning Center on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests.

Limit state is signalled in the X-PCO-API-Request-Rate-Limit, X-PCO-API-Request-Rate-Period, X-PCO-API-Request-Rate-Count, and Retry-After response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Church Management, ChMS, Rate Limiting, and Quotas.

2 Limits Exhausted: HTTP 429 X-PCO-API-Request-Rate-LimitX-PCO-API-Request-Rate-PeriodX-PCO-API-Request-Rate-CountRetry-After
Method: generated, dated 2026-07-03.
Written by API Evangelist on 2026-07-03 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Church ManagementChMSRate LimitingQuotas

Limits

Default Request Rate user
requests
100 per 20 seconds
Standard per-authenticated-user limit across all products.
High-Offset Request Rate user
requests
75 per 20 seconds
Applies to requests using an offset above 30,000.

Policies

Read the Headers
Limits can change dynamically without notice; clients should read the rate-limit headers on every response rather than hardcoding 100/20s.
Backoff on 429
On HTTP 429, wait for the number of seconds in the Retry-After header before retrying, ideally with exponential backoff and jitter.
Avoid Deep Offsets
Prefer filtering (where[]) and following pagination links over very high offsets, which trigger the stricter 75/20s limit.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/planning-center-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.