To ensure high performance, prevent overloading and ensure equitable access for all users, API limits per IP have been implemented. The purpose of API limits is to ensure that the API operates within its capacity and can handle user requests without compromising its functionality.
| Title | Limit | Description |
|---|---|---|
| Connections Per IP | 200 | The API allows a maximum of 200 connections per IP address. If this limit is reached, any additional requests will be rejected with a HTTP 429 status code to prevent overload and ensure fair access for all users. |
The API enforces a limit of 200 connections per minute per IP. If you try to send more than 200 requests in a minute from the same IP, the API will return a HTTP status code 429 (Too Many Requests).
Error Message
HTTP/1.1 429 Too Many Requests
{
"message": "rate limit exceeded"
}
If you receive this error, you will need to wait for a period of time before making new requests to the API. We recommend implementing a gradual retry logic in your application to effectively handle rate limit errors.