Rate Limiting
Rate limits, daily quotas, and how to handle 429 responses.
Rate limits
Emailens enforces per-minute rate limits and daily usage quotas.
Per-minute limits
| Auth status | Limit | Window |
|---|---|---|
| Anonymous | 30 req/min | Per IP address |
| Authenticated | 60 req/min | Per user account |
Daily quotas
| Plan | Previews/day |
|---|---|
| Anonymous (no account) | 15, counted per IP |
| Free | 30 |
| Dev ($9/mo) | 100 |
| Pro ($19/mo) | Unlimited |
Quotas are counted per UTC calendar day and reset at midnight UTC.
Response headers
Rate limit information is included in response headers:
| Header | Description |
|---|---|
X-RateLimit-Remaining | Requests remaining in current window |
Retry-After | Seconds to wait before retrying (on 429 responses) |
Handling 429 responses
When you hit a rate limit, the API returns HTTP 429:
{
"error": "Rate limit exceeded. Try again later."
}For daily quota limits:
{
"error": "Daily preview limit reached (100). Upgrade your plan for more.",
"limit": 100,
"plan": "dev"
}Retry strategy
- Read the
Retry-Afterheader - Wait the specified number of seconds
- Retry the request
Retry-After is sent on per-minute rate limits and on the anonymous daily cap.
It is not sent when a plan quota is exhausted: that resets at midnight UTC
rather than after a short window, so retrying sooner will not help.
Retry-After is sent on per-minute rate limits and on the anonymous daily cap.
It is not sent when a plan quota is exhausted: that resets at midnight UTC
rather than after a short window, so retrying sooner will not help.
For automated pipelines, use exponential backoff starting from the Retry-After value.