Command Palette
Search for a command to run...
Rate Limits
Understanding API rate limits and quotas
Fair Usage Policy
LeakZero implements sophisticated rate limiting to ensure optimal performance for all users while maintaining system stability and preventing abuse. Our intelligent rate limiting system adapts to usage patterns and provides generous limits for legitimate security operations.Current Rate Limits
Request Rate Limits
Maximum number of API requests per time window
Burst Capability
Short bursts above the per-minute limit are allowed for up to 60 seconds, enabling efficient batch processing.Data Volume Limits
Maximum data retrieval per request and time period
Smart Pagination
Use pagination for large datasets to optimize performance and stay within limits.Rate Limit Headers
Response Headers
Every API response includes rate limiting information in headers
Standard Headers
X-RateLimit-Limit: 300X-RateLimit-Remaining: 287X-RateLimit-Reset: 1640995200X-RateLimit-Window: 60Header Descriptions
LimitMaximum requests per window
RemainingRequests left in current window
ResetUnix timestamp of window reset
WindowWindow duration in seconds
Rate Limit Responses
HTTP 429 - Rate Limited
Response when rate limit is exceeded
HTTP/1.1 429 Too Many Requests
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1640995260
Retry-After: 60
{
"error": "RATE_LIMIT_EXCEEDED",
"message": "Rate limit...",
"retryAfter": 60,
"limit": 300,
"window": 60
}Recommended Handling
Best practices for handling rate limits
1
Respect Retry-After Header
Wait the specified time before retrying
2
Implement Exponential Backoff
Gradually increase retry intervals on failures
3
Monitor Rate Limit Headers
Proactively slow down when approaching limits
4
Use Efficient Pagination
Request optimal batch sizes to minimize calls
Advanced Features
Adaptive Rate Limiting
Intelligent limits based on usage patterns
Dynamic burst allowance for legitimate usage
Lower limits for suspicious activity patterns
Higher limits for verified enterprise users
Automatic adjustment based on server load
Smart Detection
Our system learns from your usage patterns to provide optimal rate limits for your specific use case.Timestamp Validation
Additional security through timestamp checking
Tolerance Window±5 minutes
Clock Skew DetectionAutomatic
Replay ProtectionBuilt-in
Warning
Requests with timestamps outside the tolerance window are rejected regardless of rate limits.Implementation Best Practices
Optimal Client Implementation
Follow these patterns for reliable API integration
Do These
- Implement exponential backoff with jitter
- Cache responses when appropriate
- Use connection pooling and keep-alive
- Monitor and log rate limit headers
- Batch requests when possible
Avoid These
- Ignoring 429 responses and retrying immediately
- Making unnecessary duplicate requests
- Using timestamps from client system clock
- Implementing aggressive retry without backoff
- Creating multiple concurrent connections per API key
Enterprise Rate Limits
Custom Rate Limits for Enterprise
Higher limits and dedicated infrastructure for enterprise customers
1,000
Requests/minute
50,000
Rows/request
20
Concurrent requests
Additional Enterprise Benefits:
- Dedicated API endpoints with isolated rate limiting
- Custom rate limit configurations per use case
- Priority routing and reduced latency
- 24/7 support and monitoring