Sentry System Rate Limits
Sentry's REST API enforces two complementary mechanisms — fixed-window requests-per-second and concurrent in-flight requests. Limits are scoped per unique caller + endpoint combination (not per token, so generating extra tokens does not bypass them). Specific numeric thresholds are not published globally and vary per endpoint; current state is exposed via X-Sentry-Rate-Limit-* headers on every response. Sentry recommends webhooks over polling to avoid throttling.
Sentry System Rate Limits is the machine-readable rate-limit profile for Sentry on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests_per_window and concurrent_requests.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Error Tracking, Observability, and Rate Limiting.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.