Skip to main content

​
Limits Table

​
Rate Limit Exceeded Response Example

​
Rate Limit Headers

The API returns rate limit information headers in every response:
Always use the rate limit headers returned in each response to dynamically adjust your request frequency. Do not hardcode limit values in your code — they may change and vary depending on the service.

​
Command Queue

*/command endpoints use a queue system:
  • Maximum queue size: 100 commands
  • Execution interval: 1 command every 5 seconds
When the queue is full, you will receive:

​
Anti-Spam Protection

After exceeding the limit, the counter does not stop but continues counting excess requests. Upon reaching 400 excess requests, a 5-minute ban is issued. If spam continues, the ban duration increases.
Stats API V2: Use a token to increase the limit from 40 to 120 requests/min. Pass the token via the Authorization: Bearer <token> header.

​
Repeat Offenders

Applications that continue sending requests after receiving 429 responses may be blocked for increasingly longer periods.
Applications that systematically violate rate limits will be blocked via Cloudflare. If you encounter a Cloudflare block page, you need to contact us by opening an API ticket on the ER:LC Discord server to have the block lifted.

​
Shared IP Hostings

The ER:LC Russia API does not support BotGhost and similar hostings with shared IP addresses. When many different applications run under one IP, they constantly hit each other’s rate limits, and there is no way to resolve this issue. For stable API access, host your service on a dedicated IP.