Quick answer
Resend documents default api rate as 10 requests per second per team. RateLimit headers expose limit, remaining, and reset state.
Verified Sep 17, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| default API rateRateLimit headers expose limit, remaining, and reset state. | 10 requests per second per team | Default | ResendSep 17, 2026 |
Why does this limit matter?
Multiple applications in the same team share a small default request budget.
This value is scoped to Default; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Aggregate calls by team and honor the Resend RateLimit response headers.
- 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
- Sending quota and API request rate are different constraints.
- 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