Understanding API Rate Limits
API requests are a powerful tool for accessing and manipulating data from our platform. However, it's important to note that these requests are subject to a rate limit in order to maintain system stability and prevent abuse.
The limit is applied per API credential / token pair (not per IP, not per endpoint, not per company).
Limit: 60 requests per 60-second sliding window.
Response when exceeded: HTTP 429 with message: “Rate limit exceeded. Please reduce request frequency.”
Rolling window: requests are counted over the previous 60 seconds (not fixed minute boundaries).
Because the limit is credential-scoped, if the same token pair is used from multiple servers/IPs they will share the same allowance.
It’s a total request limit across the API (not endpoint-specific), and it does not cap concurrent in-flight requests, just the arrival rate.
It's important for users to be aware of this rate limit and ensure that their refresh rates are set accordingly. If the rate limit is exceeded, the API request will be rejected and an error message will be returned. This can cause delays in data retrieval and potentially impact the performance of your application.
How to Prevent Exceeding the Rate Limit
To prevent exceeding the rate limit, we recommend setting your refresh rates to at least 2 minutes or longer. This will ensure that your API requests are within the allowed limit and will not be rejected.
Additionally, it's important to monitor your API usage and adjust your refresh rates if necessary. If you notice that your requests are being rejected due to the rate limit, consider increasing the refresh rate or optimizing your API calls to reduce the number of requests being made.