Rate Limiting
API rate limits and best practices.
WarpLink uses a sliding window rate limiter on all API endpoints.
All API keys are rate limited to 60 requests per minute using a sliding window algorithm.
Response Headers
Every API response includes rate limit information:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed per window |
X-RateLimit-Remaining | Requests remaining in current window |
X-RateLimit-Reset | Seconds until the window resets |
Handling Rate Limits
When the limit is exceeded, the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait.
{
"error": {
"code": "RATE_LIMIT_EXCEEDED",
"message": "Too many requests. Retry after 12 seconds."
}
}Best Practices
- Implement exponential backoff when you receive a 429 response
- Cache API responses when possible to reduce request volume
- Use the
X-RateLimit-Remainingheader to proactively throttle requests - For bulk operations, batch requests rather than making many individual calls