Rate Limits
Rate limits are an essential aspect of the Nuclia platform, ensuring fair usage and optimal performance for all users interacting with Nuclia APIs. This document outlines the rate limits enforced by Nuclia and provides guidelines for handling rate-limited responses effectively.
Introduction
There are two types of limits that Nuclia can apply to its APIs:
-
Regular API rate limits: by default, the sum of all authenticated requests in a Nuclia account can not exceed the 2400 requests per minute limit. Note that this limit can be customized on a per-account basis, so please contact Nuclia's support team if you need to increase them.
-
Ingestion Back pressure limits: Nuclia implements a back-pressure mechanism to manage ingestion pipeline overload. This mainly affects all endpoints for uploading data and creating or updating resources.
Handling Rate Limited Responses
Nuclia adheres to the HTTP standard and will return a response with 429 status codes when the limits are exceeded.
The official Nuclia API clients already have built-in mechanism for retrying requests on the event of rate limits:
However, if you are interacting directly with the API, we recommend using an exponential backoff retry strategy when limits are reached.
On the event of ingestion back pressure rate limits, the response will include a try_after key with an estimated UTC time for retrying the request. You can use this value for retrial logic as an alternative to the exponential back-off strategy.