Throttling policy

Overview

Throttling has been implemented in the HTTP OpenAPI to ensure fair usage and to maintain system stability. When the rate limit is exceeded, the application programming interface (API) responds with a 429 Too Many Requests status code along with the retry-after header indicating the number of seconds the client should wait before retrying the request.

Rate limit

The rate limit for API requests is set to 60 requests per minute. If this limit is exceeded, further requests within the same minute will be rejected with a 429 Too Many Requests response.

Note:

The computation of the number of requests is not precise as the requests are counted based on a 1 minute time window starting from the next minute. That means that more than 60 requests might be needed to get the

429 - Too Many
          Requests

error.

Retry-after header

After receiving a 429 Too Many Requests response, clients should parse the retry-after header to determine the waiting period before making another request. This header indicates the number of seconds the client must wait before retrying the request. Clients should respect this waiting period to avoid further throttling.

Impact

Throttling affects all endpoints exposed under the /api/open path. Clients making requests to any of these endpoints should be aware of the throttling policy and handle a 429 Too Many Requests response appropriately.

Example

HTTP/1.1 429 Too Many Requests
Content-Type: application/json
retry-after: 30