Rate Limiting

Each client is allowed a maximum of 60 requests per minute.

If the limit is reached, the API returns HTTP 429 Too Many Requests. The request will not be processed until the current rate window resets. The reset happens automatically after one minute.

Example response

{
  "message": "Too Many Requests"
}

Rate Limit Headers

Each response contains rate-limit information. These values help you understand how many requests remain in the current window:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 12

X-RateLimit-Limit indicates the total number of requests allowed per minute.
X-RateLimit-Remaining indicates how many requests are still available before hitting the limit.

Recommendations

Cache responses when possible to reduce repeated calls. Combine multiple operations into a single request where applicable. Monitor the rate-limit headers to avoid exceeding the allowed threshold. If you require a higher rate limit for production workloads, contact support.

Example response#

Rate Limit Headers#

Recommendations#

Example response

Rate Limit Headers

Recommendations