Bloomerang · Rate Limits

Bloomerang Rate Limits

Bloomerang does not publish fixed numeric rate limits (requests per second or per minute) for the REST API v2 in its public documentation. List endpoints such as Constituents, Transactions, and Interactions are paginated with skip/take query parameters (take defaults to 50 records per page in documented and third-party client behavior). Because Bloomerang has no sandbox environment, all API testing and integration development runs against a live production account, which in practice encourages conservative, well-paced request patterns rather than aggressive polling.

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

It captures 3 rate-limit definitions, measuring requests, records, and deliveries.

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 Nonprofit, Donor Management, CRM, Rate Limiting, and Quotas.

3 Limits Exhausted: HTTP 429
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
NonprofitDonor ManagementCRMRate LimitingQuotas

Limits

REST API v2 Requests account
requests
not published
No fixed numeric request-rate limit is documented for the REST API v2.
List Endpoint Page Size request
records
50 (default), configurable via take
Constituents, Transactions, and Interactions list endpoints are paginated with skip/take query parameters.
Webhook Delivery Retries subscription
deliveries
not published
Retry/backoff behavior for failed webhook deliveries is not documented.

Policies

Sandbox-Free Testing
Bloomerang offers no sandbox environment, so all integration development and testing occurs against live production data.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses, even without a published numeric limit.
Private Key Secrecy
The private API key grants full read/write access to the account and must be kept secret; Bloomerang recommends OAuth registration for third-party access scenarios instead of sharing a private key.

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/bloomerang-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.