Rate limits - Chataigne Docs

The Chataigne API currently allows 10,000 requests per 60 seconds for each API key. Rate limiting protects availability and prevents one integration from overwhelming the service.

Response headers

Every response reports the current state of the key’s limit:

Header	Meaning
`X-RateLimit-Limit`	Maximum number of requests in the current window.
`X-RateLimit-Remaining`	Requests remaining in the current window.
`X-RateLimit-Reset`	Time when the current window resets.

Use these headers for observability and to slow high-volume work before exhausting the quota.

When the limit is exceeded

The API returns 429 Too Many Requests with a rate_limit_error body and a Retry-After header. Do not retry before that delay has elapsed.

HTTP/1.1 429 Too Many Requests
Retry-After: 12
X-RateLimit-Limit: 10000
X-RateLimit-Remaining: 0

Retry safely

Honor Retry-After when it is present.
Add a small random delay so multiple workers do not retry at the same instant.
Limit the number of attempts.
Use idempotency keys when retrying resource creation.
Reduce concurrency for batch imports and use the maximum useful pagination size.

Node.js

async function fetchWithRateLimitRetry(url, options, attempts = 4) {
  for (let attempt = 0; attempt < attempts; attempt += 1) {
    const response = await fetch(url, options);
    if (response.status !== 429) return response;

    const retryAfter = Number(response.headers.get('retry-after') ?? 1);
    const jitterMs = Math.floor(Math.random() * 250);
    await new Promise((resolve) => setTimeout(resolve, retryAfter * 1000 + jitterMs));
  }
  throw new Error('Chataigne API rate limit retry budget exhausted');
}

Limits may evolve. Read the response headers instead of hard-coding the current quota into your application logic.

​Response headers

​When the limit is exceeded

​Retry safely

Response headers

When the limit is exceeded

Retry safely