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, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests.

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 Throttle: 429
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