Rate Limits

📘Note:
At present, the total number of requests per Account per minute is 100 (the total number of requests will be adjusted according to related needs later).
Recommended Practice
To ensure efficient allocation of resources, include an API Key in all requests to Polluxweb.

Rate Limiting Policy

With API Key

If usage is within the daily limit:

Requests are limited to 15 QPS (queries per second).

Exceeding this limit will result in a 503 error and denial of access.

If usage exceeds the daily limit:

Requests are limited to a very low rate, such as 5 QPS.

Exceeding this limit will result in a 503 error and denial of access.

Without API Key

Requests are dynamically rate-limited.

Exceeding the rate limit triggers a 30-second block, during which requests will be denied with a 403 error.

After 30 seconds, the block will be lifted.

Identifying Rate-Limited Requests

If your request is rate-limited, you will receive an HTTP status code of 4xx or 5xx with an error message.

Example Response for v1 Interface:

{
    "Success": false,
    "Error": "The key exceeds the frequency limit(100), and the query server is suspended for 30s",
    "StatusCode": 403
}

{
    "Error": "The key exceeds the frequency limit(100), and the query server is suspended for 60s"
}

What to Do if Rate-Limited

If you encounter rate limiting:

Ensure API Key Usage

Include your API Key in the request header to avoid stricter limits or rejections.

Optimize DApp Requests

Limit the number of requests made during DApp initialization.

Avoid Excessive Polling

The Pollux network generates a block approximately every 3 seconds. Polling data more frequently is unnecessary and inefficient.

Rate Limiting Policy#

With API Key#

Without API Key#

Identifying Rate-Limited Requests#