429 errors or hitting monthly quotas, this guide covers how to identify the issue and adjust your sending approach.
Rate Limit Overview
Lettr applies limits at the API request level, per authentication credential:| Limit | Threshold | Window |
|---|---|---|
| Standard API rate limit | 300 requests | 5 minutes |
| High-volume API rate limit | 2,000 requests | 5 minutes |
| Authentication failures | 5 failures | 5 minutes (triggers 15-minute block) |
| Recipients per request | 50 | Per request (combined to, cc, bcc) |
High-volume rate limits are available on Pro and Enterprise plans. Contact sales@lettr.com to discuss your volume needs.
Rate Limit Response
When you exceed the rate limit, the API returns an HTTP429 status code with the following response body:
retry_after field indicates how many seconds you should wait before making another request.
Handling Rate Limits — Implementing Backoff
When your application receives a429 response, it should pause and retry with exponential backoff. The following example reads the retry_after value from the response body and backs off accordingly:
429, parse the JSON body and wait for the number of seconds specified in retry_after before retrying.
Efficient Sending
Each API request supports up to 50 recipients across theto, cc, and bcc fields combined. To minimize the number of API calls and stay within rate limits, always fill each request to capacity before sending the next.
Monthly Email Quotas
Each plan includes a monthly email quota. Every recipient on every request counts toward this quota.| Plan | Monthly Quota |
|---|---|
| Free | 3,000 emails |
| Pro 50K | 50,000 emails |
| Pro 100K | 100,000 emails |
| Pro 200K | 200,000 emails |
| Pro 500K | 500,000 emails |
| Pro 1M | 1,000,000 emails |
| Enterprise | Custom |
Emails beyond your tier limit are charged at $0.80 per 1,000 emails. Check your current plan details in the Lettr dashboard under Settings > Billing.
Monitoring Usage
You can track your current API usage and monthly email quota in the Lettr dashboard:- Go to Dashboard > Usage to view your current month’s email volume.
- Review your remaining quota and historical usage trends.
- Set up alerts if your usage is approaching the plan limit.
Queuing Strategies
For large sends, queue outbound requests and pace them with a controlled delay to stay within rate limits:setTimeout pacing. For production workloads, consider persisting the queue to a database so incomplete sends can be resumed after a restart.
Best Practices
Implement exponential backoff
Implement exponential backoff
Always handle
429 responses by reading the retry_after value and backing off exponentially. Never retry immediately — this worsens throttling and can extend the cooldown period.Batch recipients efficiently
Batch recipients efficiently
Include up to 50 recipients per API request. Sending one recipient per request wastes your rate limit allowance and dramatically slows throughput.
Monitor usage in the dashboard
Monitor usage in the dashboard
Regularly check your email volume and quota in the Lettr dashboard. Catching usage spikes early prevents disruptions to scheduled campaigns.
Use webhooks instead of polling
Use webhooks instead of polling
Rather than polling the API repeatedly to check email status, configure webhooks to receive delivery events in real time. This eliminates unnecessary API calls and keeps you well under rate limits.
Queue large sends
Queue large sends
For sends to thousands of recipients, queue requests and pace them with a consistent delay. This avoids bursts that trigger rate limiting and gives you control over throughput.
Increasing Your Limits
If you are consistently hitting rate limits or approaching your monthly quota, you have two options:- Upgrade your plan. Higher plans include larger monthly quotas and access to high-volume rate limits. Visit Settings > Billing in the dashboard to compare plans.
- Contact sales for Enterprise. If you need custom rate limits, dedicated infrastructure, or quotas beyond 500,000 emails per month, reach out to sales@lettr.com.
If you are experiencing rate limit issues that seem incorrect — for example, receiving
429 errors well below the documented thresholds — contact support@lettr.com with your API key prefix and timestamps of the affected requests.