The Reporting API endpoints can use these types of rate limiting:

• Request count-based rate limiting

• Cost-based rate limiting

• Async flow rate limiting

Check the report documentation under Available reports to see which rate limiting types the report uses.

Request count-based rate limiting

The request count-based rate limiting restricts the serving of API responses based on the number of requests made in a time interval of one minute.

The rate limiting value is configured individually for each API endpoint. Check the report documentation under Available reports.

If multiple API clients within the same account are calling the API, the rate limit is applied globally to all the API clients at a given time. When the limit is reached, the API responds with an HTTP 429 error, and you can't make new requests until the next rate-limiting bucket refill. You need to consider the limit when you call successive operations as part of a loop.

These response headers show the request count-based rate limiting values:

Cost-based rate limiting

The cost-based rate limiting focuses on the resources consumed by each API request. The cost value is assessed based on factors such as the computational resources used. This can be correlated with metrics like the volume of data processed, including the data range and the number of business objects, or the complexity of operations involved in generating results, such as multiple aggregations, complex filtering, or heavy regular expressions.

The API endpoints implement a leaky bucket algorithm that keeps track of the limit consumed by an account and an API endpoint. The client receives a rate limiting response after exhausting all allocated tokens in a time interval. Upon receiving this response, the client should pause sending requests until the specified time. If multiple requests encounter rate limits, consider introducing an additional jitter beyond the bucket refill time to help reduce the load on the system and get a successful response.

These response headers show the cost-based rate limiting values:

Async flow rate limiting

There is a limit of concurrent asynchronous POST requests for an account. These are requests which are either actively being processed or waiting for the processing, for which the data isn’t ready yet. Check the rate limiting value in the report documentation under Available reports.

These response headers show the rate limiting values for the async flow:

Additionally, these response headers show the hit-based rate limits for the GET data endpoint: