Benevity · Rate Limits

Benevity Rate Limits

Benevity does not publish fixed numeric request-rate limits for the Giving, Causes, Spark, or Location Services APIs in its public developer documentation. OAuth 2.0 access tokens are valid for 3600 seconds (expires_in), and the docs explicitly advise reusing a token until expiry rather than requesting a new one per call "to optimize performance and avoid rate limiting issues" - implying a token-request limiter exists on /oauth2/token even though no number is published. The production API targets ~99.9% uptime outside of a recurring maintenance window (Saturday nights, 6:00pm-12:00am MT, roughly every 5 weeks); a separate sandbox (api.benevity-staging.org) targets uptime during business hours only.

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

It captures 4 rate-limit definitions, measuring requests and availability.

The profile also includes response codes documented for throttled.

Tagged areas include Corporate Social Responsibility, Workplace Giving, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Corporate Social ResponsibilityWorkplace GivingRate LimitingQuotas

Limits

OAuth2 Token Requests client
requests
not published
Docs advise reusing the access_token until near expiry rather than fetching a new one per request.
Giving / Causes / Receipts API Requests account
requests
not published
No numeric limit documented for the skyline.benevity.org host.
Spark API Requests account
requests
not published
No numeric limit documented for the api.benevity.org host.
Scheduled Maintenance Window platform
availability
weekly Saturday 6:00pm-12:00am MT, roughly every 5 weeks
Production targets ~99.9% uptime outside this window per the releases page.

Sources