Rate limits

Overview

To protect the gym's system from performance issues during normal use of EVO, the APIs follow a rate limits system. These restrictions ensure that the environment remains stable, even under high usage load.

The rate limits criteria are described below:

Rate Limit Criteria

1. Limit per Second (per IP)

Limit: 5 requests per second for the same IP.

Behavior after the limit is reached:

Returns with status code 429 (Too Many Requests).

Wait 1 second before making new requests.

2. Limit per Minute (per IP)

Limit: 40 requests per minute for the same IP.

Behavior after the limit is reached:

Returns with status code 429 (Too Many Requests).

Wait 1 minute before making new requests.

💎 Customers of API PRO do not have the per minute limit.

3. Limit per Hour (per API Key)

Limit: 10,000 requests per hour for the same API key.

Behavior after the limit is reached:

The API key will be blocked for 1 hour.

Returns with status code 429 (Too Many Requests).

Details:

The block is applied to the specific key, regardless of the IP that made the requests.

All requests made with this key count towards the limit.

4. Rate Limit per Hour (per Gym DNS)

Limit: 20,000 requests per hour for the same gym DNS.

Behavior after the limit is reached:

All keys linked to the gym's DNS will be blocked for 1 hour.

Returns with status code 429 (Too Many Requests).

Details:

The block is applied to the gym (validated by DNS), regardless of the IP or API key used.

All requests made by the gym count towards the limit.

Exemption Window

Time: From 12 AM to 5 AM.

During this period, there are no limits on the number of requests per hour, per DNS, or IP. However, the limits on requests per second and per minute remain active. In other words, it is possible to make requests in larger volumes without these limits being applied, but the restrictions on the number of requests per second and per minute will still be in effect.

Batch requests can be made during this period.

Operations that require a high volume of requests can take advantage of this window.

Summary of Limits

Limit Type	Limit	Block	Status Code
Per Second (per IP)	5 requests	for 1s	429
Per Minute (per IP)	40 requests	for 1m	429
Per Hour (per Key)	10,000 requests	for 1h	429
Per Hour (per DNS)	20,000 requests	for 1h	429

Best Practices to Avoid Rate Limits

Implement a retry system with backoff: When receiving a status code 429, wait before trying again.

Avoid unnecessary requests: Ensure that only essential requests are made.

Take advantage of the exemption window: Schedule batch requests between 12 AM and 5 AM, when the hourly limits for DNS and IP are not applied, but be mindful of the limits on requests per second.

Monitor your requests: Use logs to track and adjust your volume of API calls.

Overview#

Rate Limit Criteria#

1. Limit per Second (per IP)#

2. Limit per Minute (per IP)#

3. Limit per Hour (per API Key)#

4. Rate Limit per Hour (per Gym DNS)#

Exemption Window#

Summary of Limits#

Best Practices to Avoid Rate Limits#

Overview

Rate Limit Criteria

1. Limit per Second (per IP)

2. Limit per Minute (per IP)

3. Limit per Hour (per API Key)

4. Rate Limit per Hour (per Gym DNS)

Exemption Window

Summary of Limits

Best Practices to Avoid Rate Limits