Bugsnag Rate Limits
BugSnag publishes the rate-limit MECHANISM for the Data Access API — the window, the exhaustion status and the three response headers — but not the numeric ceiling. The limit is discoverable only at runtime, from X-RateLimit-Limit on a successful response. Read verbatim from the SmartBear developer portal's Rate Limiting guide on 2026-09-17; the previous version of this artifact carried a "60 requests per minute" figure sourced from the retired bugsnagapiv2.docs.apiary.io documentation, which is no longer published anywhere and is therefore not restated here.
Bugsnag Rate Limits is the machine-readable rate-limit profile for Bugsnag on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring requests_per_window and events_or_spans_per_month.
Limit state is signalled in the limit, remaining, retryAfter, and note response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled.
Tagged areas include Rate Limiting and Error Monitoring.
limitremainingretryAfternote
Limits
Sources
- https://developer.smartbear.com/bugsnag/docs/data-access-rate-limiting
- https://www.bugsnag.com/pricing/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.