Usage limits and requests throttling

The maximum request rate is 200 requests per second. If you exceed this limit, further requests are rejected until the start of the next second. Refer to the corresponding response headers for details.

This API is also available with a dedicated load balancer and premium endpoint to enable faster querying as part of our Premium API Services and Enterprise API Packages.

When you exceed the limit

Requests over the limit receive an HTTP 429 (Too Many Requests) response:

{
  "ErrorMessage": {
    "errorCode": "AUTHENTICATE_06",
    "msg": "rate limit exceeded"
  }
}

Response headers

Every response includes your current rate-limit status:

X-RateLimit-Limit
Your maximum requests per window.
X-RateLimit-Remaining
Requests remaining in the current window.
X-RateLimit-Reset
Unix timestamp when the window resets.


On a 429 response, an additional header is sent:

Retry-After
Number of seconds to wait before retrying.

Recommended handling

  • Watch X-RateLimit-Remaining and throttle your request rate before it reaches zero.
  • On a 429, wait for the number of seconds given in Retry-After before retrying, rather than retrying immediately.