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.
Limits
Policies
Sources
- https://support.breezechms.com/hc/en-us/articles/360001324153-API-Advanced-Custom-Development
- https://app.breezechms.com/api
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/breeze-chms-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.