Rate limiting

The Indexing Insight API uses rate limiting to ensure fair usage of the API. The rate limits are applied to the API key.

To maintain API performance and availability, all clients are limited to 60 requests per minute. If this limit is exceeded, the API will return a 429 Too Many Requests HTTP status code.

Rate limit headers

When you make a request to our API, we include the following headers in the response:

Header	Description
Retry-After	Number of seconds to wait before retrying
X-RateLimit-Limit	Max requests allowed per time window
X-RateLimit-Remaining	Remaining requests in the current time window
X-RateLimit-Reset	Time when the rate limit resets (in UNIX time)

Below is an example of the rate limit headers in the API response:

Rate limit response

When you exceed your allowed number of requests, the API will respond with a 429 Too Many Requests HTTP status code.

The response will also include the following JSON body:

{
  "error": "rate_limit_exceeded",
  "message": "Too many requests. Please try again later.",
  "status": 429
}

When you recieve a 429 Too Many Requests use the Retry-After header to know how long to wait before making another request.

Rate limit headers#

Rate limit response#

Rate limit headers

Rate limit response