Rate Limiting Guide
Understanding API rate limits and implementing efficient request patterns.
Overview
Rate limiting protects our service from abuse and ensures fair usage for all customers. This guide explains our rate limits, how to monitor your usage, and strategies for optimizing your API calls.
Rate Limit Structure
Current rate limits for different endpoint types
| Endpoint Type | Rate Limit | Window | Burst Limit |
|---|---|---|---|
| Single Validation | 100 requests | per minute | 200 |
| Bulk Validation | 10 requests | per minute | 20 |
| Target Groups | 50 requests | per minute | 100 |
| Offers Management | 30 requests | per minute | 60 |
Rate Limit Headers
Every API response includes rate limit information in the headers:
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 1640995200
X-RateLimit-Window: 60Monitoring Rate Limits
Track your API usage and implement proactive monitoring
Reading Rate Limit Headers
Loading syntax highlighting...Proactive Rate Limit Management
Loading syntax highlighting...Optimization Strategies
Techniques to maximize API efficiency and minimize rate limit issues
Strategy 1
Use Bulk Operations
Process multiple items in single requests when possible:
Loading syntax highlighting...Strategy 2
Implement Caching
Cache validation results to avoid repeated API calls:
Loading syntax highlighting...Strategy 3
Batch Processing
Process large datasets in manageable chunks:
Loading syntax highlighting...Best Practices
Essential guidelines for efficient API usage
Do
- • Monitor rate limit headers in every response
- • Use bulk operations for multiple validations
- • Implement caching to reduce redundant requests
- • Add delays between batch operations
- • Use exponential backoff for retries
- • Implement graceful degradation when rate limited
Don't
- • Ignore rate limit headers
- • Make parallel requests without coordination
- • Retry immediately after being rate limited
- • Process large datasets without batching
- • Cache results indefinitely
- • Assume unlimited API capacity
Enterprise Rate Limits
Higher limits and custom features for enterprise customers
Enterprise customers can request higher rate limits based on their usage patterns. Contact our sales team to discuss custom rate limit requirements.
Custom Rate Limit Features
- • Dedicated API endpoints with higher limits
- • Custom rate limit windows (hourly, daily)
- • Priority queuing for high-volume operations
- • Real-time rate limit monitoring dashboard
- • Webhook notifications for rate limit events
Troubleshooting
Common rate limiting issues and solutions
Getting 429 errors frequently
- Check if you're making too many concurrent requests
- Implement request queuing and rate limit monitoring
- Use bulk operations instead of individual calls
- Add caching to reduce redundant requests
Unexpected rate limit resets
- Rate limits are per-minute rolling windows
- Check X-RateLimit-Reset header for exact reset time
- Account for clock drift between systems
- Monitor your request patterns for spikes
Performance issues with large datasets
- Use bulk validation endpoints (max 1000 emails per request)
- Implement asynchronous processing for very large datasets
- Process data in batches with appropriate delays
- Consider upgrading to enterprise limits if needed