Rate limit information is returned through response headers, allowing clients to monitor their current quota and adjust request throughput accordingly.
Headers
These headers are returned by Unipile's rate limiter. In particular, a 429 response with type: api/too_many_requests includes retry-after, which tells you when to retry. A 429 returned by a provider (type: provider/too_many_requests) means the provider was reached before Unipile stopped the request; it may not provide an equally reliable retry window. See Rate Limits for how to handle each case.
| Header | Description |
|---|---|
x-ratelimit-limit | Maximum number of requests allowed during the current time window. |
x-ratelimit-remaining | Number of requests remaining in the current time window. |
x-ratelimit-reset | Number of seconds until the current time window resets. |
retry-after | Number of seconds to wait before retrying a request after a rate limit has been exceeded. This header is only returned with 429 Too Many Requests responses. |
Example
http HTTP/1.1 200 OK
x-ratelimit-limit: 50
x-ratelimit-remaining: 12
x-ratelimit-reset: 24In this example:
- The current limit is 50 requests.
- 12 requests remain available.
- The rate limit window will reset in 24 seconds.
Related Documentation
For details about rate limit policies, quotas, provider-specific restrictions, and enforcement rules, see the Rate Limits guide.