The Cleverbridge platform limits you to a maximum of 150 requests per second from an IP address or range. All API requests count towards the rate limit.
HTTP 429 Status Code
When an individual IPv4 address or an IPv6/64 IP range exceeds the per-second request limit, further requests to our API are blocked with an HTTP 429 status code until the block time has expired. This happens after one minute. The HTTP response contains a
Retry-After header to indicate when you can resume sending requests.
HTTP/1.1 429 Too Many Requests Content-Type: text/html Retry-After: 60
How to Avoid Reaching the Rate Limit
The most likely cause of an
HTTP 429 Too Many Requests error is that you perform a batch operation that sends multiple API requests in parallel. To avoid reaching the rate limit with batch operations:
- Send API requests in serial, which means that the next call included in the batch operation cannot be made until the current call is completed.
- Limit concurrent threads that make requests to a maximum of four.
Updated 5 months ago