Prompt
why is my email api throttling requests
Latest observation
Nov 17, 2026
OpenAI APIWeb search: off
Your email API is probably throttling requests because it’s hitting a rate limit or a sending policy enforced by the provider. Common reasons:
- Too many requests too quickly: bursts of API calls exceed per-second/minute limits.
- Daily/hourly send cap: you’ve reached an account, domain, or IP quota.
- Concurrent requests: too many parallel sends trigger protection.
- Bad reputation / spam signals: the provider may slow you down if your traffic looks suspicious.
- Recipient/domain limits: some providers throttle by destination domain to protect deliverability.
- API key/app limits: separate limits may apply per key, project, or tenant.
- Temporary provider issues: the service may be applying adaptive throttling during peak load.
What to check:
- HTTP response code/body: look for
429 Too Many Requests,rateLimitExceeded,throttled, or aRetry-Afterheader. - Provider dashboard/logs: quota usage, send limits, and suppression events.
- Request pattern: bursts, retries without backoff, or parallel workers.
- Mailing behavior: many messages to the same domain or invalid recipients.
- Account status: new account warm-up, verification, or policy enforcement.
How to fix it:
- Add exponential backoff with jitter
- Respect
Retry-After - Queue sends and smooth bursts
- Reduce parallelism
- Batch where supported
- Warm up new domains/IPs gradually
- Clean recipient lists and reduce bounces/complaints
If you want, paste:
- the API response/error
- your email provider
- a sample of your send rate pattern
and I can help pinpoint the exact cause.