Quick answer
Stripe documents default endpoint throughput as 25 requests per second. Endpoint-specific and resource-specific exceptions can be lower or higher.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| default endpoint throughputEndpoint-specific and resource-specific exceptions can be lower or higher. | 25 requests per second | Most API endpoints | StripeAug 22, 2026 |
Why does this limit matter?
Traffic can stay below the account global limit yet overload one hot endpoint.
This value is scoped to Most API endpoints; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Break request metrics down by endpoint, method, account, and rate-limit reason.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Search endpoints are documented at 20 requests per second and use separate scope.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related