Rate limits

Rate limits protect the API from overload and maintain stable operation for all clients.

How a limit manifests

When the limit is exceeded, the API returns HTTP 429 Too Many Requests with a Retry-After header and response body:

HTTP/1.1 429 Too Many Requests
Retry-After: 10

{
  "Code": "RATE_LIMIT_EXCEEDED",
  "Message": "Too many requests. Please try again later.",
  "RetryAfterSeconds": 10
}

The RetryAfterSeconds field contains how many seconds you should wait before the next attempt. The same value is also in the Retry-After header.

How to handle a rate limit

1. Do not repeat the request immediately.
2. Wait the number of seconds indicated by RetryAfterSeconds (or the Retry-After header).

Specific limit for calls to the export status endpoint

Endpoint GET /api/v1/ExportResult/Status/{idExportJob} has a stricter dedicated limit across all plans:

• max 10 calls per 60 seconds per API key,
• if exceeded, the API returns 429 Too Many Requests (RATE_LIMIT_EXCEEDED, Retry-After, RetryAfterSeconds).

Practical recommendations

• Limit client-side parallelism – send requests sequentially, not all at once.
• For exports, prefer callback URL or email notification instead of frequent status polling.