Rate limiting
Fluentax throttles the number of API calls that can be made by any given client (authenticated user or service account) in a given period in order to maintain a high level of service and prevent DoS scenarios.
Rate limits vary by API endpoint. See the specific API documentation for more information.
Response header for API requests
When you make an API request, the response header contains the following information:
| Name | Description | Type | Example |
|---|---|---|---|
| X-Rate-Limit-Limit | The rate limit period that is applicable for the current request (eg. 1m, 12h, 1d) | string | 15m |
| X-Rate-Limit-Remaining | The number of requests left for the current rate-limit window | integer | 997 |
| X-Rate-Limit-Reset | UTC date time (ISO 8601) when the rate limit resets | string | 2021-10-06T18:25:20.6787472Z |
Respect rate limits. Rate limits are always available in the response headers when you make an API request, so you can analyze this information and delay your next request if necessary. This can help you to avoid receiving HTTP 429 Too Many Requests responses.
HTTP 429 Too Many Requests
If your request exceeds a certain rate limit, you will receive an HTTP 429 Too Many Requests response status code. The Retry-After header indicates how many seconds you must wait before making your next request.
| Name | Description | Type | Example |
|---|---|---|---|
| Retry-After | Indicates how long to wait before making a new request | integer | 45 |
If your application uses an automatic retry logic, be sure to delay your retry request by the Retry-After value for this status code.