Skip to main content
Skip table of contents

API Rate Limit

The new API rate limit could have an impact on the way you implemented the API’s. We move from 300 req/60 seconds, to a per second. The API use will have to spread over time and the re-try mechanism needs to be in line with the X-Rate-Limit-Remaining HTTP headers.

API Rate Limit

An API rate limit will be applied to protect our platforms from excessive resource usage caused by external attacks or misconfiguration from our customers. We will count API requests and return an HTTP 429 (Too Many Requests) response when the quota is exceeded. If you reach the limit, you will need to wait for the next Rate-Limit-Reset before we process additional requests.

Rate limit policy

·   Number of total request: The actual amount that has been set for your account will be visible in the http headers.  Default will be set to 2.

·   Period of rate limiting: 1 sec

HTTP Headers

We have included some extra HTTP headers informing the client about its current usage of the API:

·   X-Rate-Limit-Limit: the number of allowed requests in the current period

·   X-Rate-Limit-Remaining: the number of remaining requests in the current period

·   X-Rate-Limit-Reset: the number of seconds left in the current period. This header is crucial for managing API usage effectively and avoiding hitting the rate limit.

Example: 

If the X-Rate-Limit-Reset header returns a value of 1, it means that the rate limit will reset in one second. Clients can use this information to implement retry logic and avoid receiving HTTP 429 (Too Many Requests) responses. The client can programmatically wait for the specified time before making new requests.

Sample Response Headers:

HTTP/1.1 200 OK

X-Rate-Limit-Limit: 2

X-Rate-Limit-Remaining: 1

X-Rate-Limit-Reset: 1

In this example, the client has 1 requests remaining out of a limit of 2, and the rate limit will reset in 1 second.

API response times

API response times can vary based on several factors, including the type of API or method used. The complexity of the request, backend data processing, and network conditions all play a role in determining the time it takes to receive a response.

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.