Rate limiting

The API enforces per-client rate limits to ensure fair usage and service stability.

Default limits

Each client account has a default limit of 60 requests per minute. This applies across all endpoints and is tracked by client ID, not by IP address. Your specific limit depends on your plan tier and can be viewed in the dashboard.

Rate limit response

When you exceed your limit, the API returns a 429 status code:

{
  "error": "RATE_LIMITED",
  "message": "Rate limit exceeded",
  "statusCode": 429
}

Handling rate limits

Use exponential backoff with jitter when you receive a 429 response:

async function requestWithBackoff(fn, maxRetries = 3) {
  for (let attempt = 0; attempt < maxRetries; attempt++) {
    const response = await fn();
    if (response.status !== 429) return response;

    const delay = Math.min(1000 * 2 ** attempt, 30000);
    const jitter = delay * (0.5 + Math.random() * 0.5);
    await new Promise((resolve) => setTimeout(resolve, jitter));
  }
  throw new Error('Rate limit exceeded after retries');
}

Best practices

Batch submissions rather than sending many requests in quick succession.
Use webhooks instead of polling job status repeatedly. See webhooks.
Stream progress with SSE instead of polling the job status endpoint.

Getting started

Platform

Moderation

Default limits

Rate limit response

Handling rate limits

Best practices

​Default limits

​Rate limit response

​Handling rate limits

​Best practices

Default limits

Rate limit response

Handling rate limits

Best practices