Platform
Rate Limits
Render25 enforces rate limits on API requests and email volume to maintain platform stability and protect deliverability.
API Rate Limits
| Endpoint | Limit | Window |
|---|---|---|
POST /v1/email/send | 1,000 requests | per minute |
GET /v1/email/logs | 60 requests | per minute |
All other endpoints | 120 requests | per minute |
Tip
Limits are per API key. If you need higher throughput, contact support to have your limits increased.
Monthly Volume Limits
| Plan | Monthly emails | Max recipients per request |
|---|---|---|
| Free | 3,000 | 10 |
| Starter | 50,000 | 50 |
| Growth | 500,000 | 50 |
| Business | Unlimited | 100 |
Rate Limit Headers
Every API response includes rate limit information in the response headers:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed per window |
X-RateLimit-Remaining | Requests remaining in current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
Retry-After | Seconds to wait (only present when rate limited) |
Handling Rate Limit Errors
When a rate limit is exceeded, the API returns a 429 Too Many Requests response. Implement exponential backoff and retry after the Retry-After interval.
Note
Sending emails in batches and using the
to array (up to 50 recipients per request) is the most efficient way to stay within limits.