Rate Limit

Each API key is subject to a predetermined request limit per minute. The specific rate limit assigned depends on the API key’s configuration and intended use case. Understanding and respecting these limits will prevent failures from valid requests.

Exceeding Rate Limit

Once the rate limit is reached, further requests will be rejected until the limit resets. When this occurs, the API returns a 429 Too Many Requests status code, includes a Retry-After header specifying how many seconds to wait before retrying, and provides a structured error message in JSON format. Proper handling of rate limit responses allows clients to implement back-off strategies and retry logic without degrading performance.

Any request made after reaching the request rate limit will return the following JSON:

{ "error":"Exceeded Request Limit!" }

Additionally, the response header will include the following attribute:

    HTTP/1.1 429 Too Many Requests
    Retry-After: {delta}

Parameter	Description
delta	Number of seconds to delay until reattempting.