Breeze ChMS · Rate Limits

Breeze Chms Rate Limits

The Breeze ChMS API enforces a request-rate limit of roughly 20 requests per minute per account API key. Breeze recommends waiting about 3.5 seconds between calls to stay under the limit; exceeding it results in a temporary block. The limit applies across the whole API surface (people, tags, events, attendance, giving, funds, pledges, forms, volunteers, and account) since all endpoints share the same Api-Key credential and church subdomain. There are no separate published per-endpoint quotas, and there is no data volume or seat-based API cap - the constraint is request frequency.

Breeze Chms Rate Limits is the machine-readable rate-limit profile for Breeze ChMS on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, seconds, and messages.

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.

3 Limits Throttle: 429
Church ManagementChMSRate LimitingQuotas

Limits

API Requests account
requests
~20 per minute
Shared across all endpoints for a given church subdomain and Api-Key.
Recommended Spacing account
seconds
~3.5 seconds between calls
Breeze's recommended delay to stay under the per-minute limit.
Text Messaging Allowance account
messages
250 per month included
Product-level messaging allowance, not an API request limit; overage billed per message.

Policies

Temporary Block
Exceeding the request-rate limit results in a temporary block until the window resets.
Backoff Strategy
Implement spacing (~3.5s) and exponential backoff with jitter; honor 429 responses and retry after the window resets.
Caching
Cache reference data such as funds, tags, calendars, and profile fields to minimize repeated calls against the shared rate limit.

Sources