Skip to main content

Rate Limit Optimization

Want to send more emails faster without hitting rate limits? Here’s how to optimize your API usage and handle rate limits like a pro.

πŸš€ Understanding Rate Limits

Default limit

Most endpoints allow 100 requests per minute per IP address, counted separately for each endpoint. Authentication endpoints are stricter. The Rate limiting page lists every limit and explains the headers and the 429 response.

Rate Limit Headers

Every response includes these headers:

⚑ Optimization Strategies

1. Batch Your Requests

Instead of sending emails one by one:

2. Use Connection Pooling

Keep connections alive:

3. Implement Caching

Cache frequently accessed data:

πŸ”„ Rate Limit Handling

Exponential Backoff

Jitter Implementation

Add randomness to prevent thundering herd:

πŸ“Š Monitoring & Analytics

Track Rate Limit Usage

Predictive Scaling

🎯 Best Practices

1. Pre-warm Your Sending

2. Use Multiple SMTP Providers

3. Optimize Request Size

🚨 Common Pitfalls

1. Ignoring Rate Limit Headers

2. Synchronous Processing

3. No Error Recovery

πŸ“ˆ Performance Metrics

Track these metrics to optimize performance:
  • Requests per second: Target 50+ RPS
  • Rate limit hits: Keep under 1%
  • Average response time: Target < 200ms
  • Error rate: Keep under 0.1%
  • Throughput: Emails sent per minute

πŸ› οΈ Tools & Libraries

Node.js Libraries

Python Libraries

Go Libraries

πŸ“ž Need Help?

If you’re hitting rate limits frequently:
  1. Review your sending patterns - are you batching properly?
  2. Check your SMTP configuration - are you using multiple providers?
  3. Monitor your usage - are you tracking rate limit headers?
  4. Contact support for custom rate limit increases
Support: team@xem.email Community: Discord