Rate Limits

​

Limit behavior

{
  "success": false,
  "error": { "code": "RATE_LIMITED", "message": "ThrottlerException: Too Many Requests" }
}

HTTP/1.1 429 Too Many Requests

​

Relevant headers

​

Handling throttling

• Treat 429 RATE_LIMITED as a signal to slow down, not a bug to route around by hammering the endpoint faster.
• Apply backoff per endpoint — a limit on renew-number doesn’t mean your other calls are also throttled, so don’t globally pause your whole integration in response to one endpoint’s 429.
• Never retry a 429 immediately in a tight loop; it will not succeed sooner and behaves poorly for every other caller sharing your account’s limit.

​

Recommended backoff strategy

async function withRetry(fn, { maxAttempts = 5, baseDelayMs = 1000 } = {}) {
  for (let attempt = 1; attempt <= maxAttempts; attempt++) {
    try {
      return await fn();
    } catch (err) {
      const retryable = err.status === 429 || err.status >= 500;
      if (!retryable || attempt === maxAttempts) throw err;
      const delay = baseDelayMs * 2 ** (attempt - 1) * (0.5 + Math.random());
      await new Promise((r) => setTimeout(r, delay));
    }
  }
}

​

Next steps

• Errors for the full status-code and retry matrix.
• Security & Best Practices for how rate-limit handling fits into a production-ready client.