Quick answer
SendGrid documents endpoint-specific api rate as Endpoint specific; exposed in rate-limit headers. SendGrid documents 429 handling without publishing one universal number for every endpoint.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| endpoint-specific API rateSendGrid documents 429 handling without publishing one universal number for every endpoint. | Endpoint specific; exposed in rate-limit headers | v3 API | Twilio SendGridAug 22, 2026 |
Why does this limit matter?
A fixed global throttle can be either wasteful or unsafe when endpoints have different capacity.
This value is scoped to v3 API; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Read rate-limit headers on the exact endpoint and back off after 429.
- 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
- Mail sending quota and management API request rate are separate controls.
- 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