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

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

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