Rate limiting

There is one limit per client address, across all API routes: 1000 requests per 60 seconds unless the instance sets GLOBAL_RATE_LIMIT_PER_MIN (which can also turn it off). Static files are not counted. A request over the limit is answered with 429, a Retry-After header in seconds, and:

json

{
  "status": false,
  "code": "server_busy",
  "statusText": "The server is busy. Try again in a moment.",
  "message": "The server is busy. Try again in a moment.",
  "retryAfter": 12
}

On a 429, wait retryAfter seconds and send the same request again. The response headers RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset show where the caller stands.

Rate limiting ​

Rate limiting