Rate limits

Limits are applied per team across all API tokens belonging to that team.

Current limits

Two windows are enforced simultaneously on every request:

Window	Limit
Per-minute (burst)	1,000 requests / minute
Per-day (daily cap)	20,000 requests / day

A request is accepted only if both windows have budget remaining. If either window is exhausted, the API returns 429 Too Many Requests.

To discuss a different limit for a planned workload, contact team@qwairy.co with the expected request volume.

Rate-limit headers

After successful authentication, API responses include headers for both windows. A 429 response also includes Retry-After.

Header	Description
`X-RateLimit-Limit`	Per-minute request cap
`X-RateLimit-Remaining`	Requests remaining in the current minute window
`X-RateLimit-Reset`	ISO 8601 timestamp when the minute window resets
`X-RateLimit-Daily-Limit`	Per-day request cap
`X-RateLimit-Daily-Remaining`	Requests remaining in the current day window
`X-RateLimit-Daily-Reset`	ISO 8601 timestamp when the day window resets
`Retry-After`	Seconds to wait before retrying, based on the limit actually hit (only set on `429`)

Synthetic headers

X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 873
X-RateLimit-Reset: 2026-04-07T09:13:00.000Z
X-RateLimit-Daily-Limit: 20000
X-RateLimit-Daily-Remaining: 4211
X-RateLimit-Daily-Reset: 2026-04-08T00:00:00.000Z

Check both windows. A request can be rejected when the daily cap is exhausted even if the per-minute budget remains, and vice versa.

Handle rate limits

When either window is exceeded, the API returns 429 Too Many Requests with a body indicating which window was hit:

{
  "error": "Too Many Requests",
  "limit": "daily",
  "message": "Daily rate limit (20000/day) exceeded. Please try again in 32451 seconds.",
  "retryAfter": 32451
}

The limit field is either "burst" or "daily". Honor Retry-After, which is calculated from the window that blocked the request.

Retry practices

Honor Retry-After

Use the Retry-After header as-is. It already reflects whichever window (minute or day) is the real blocker.

Watch both remaining headers

Monitor X-RateLimit-Remaining and X-RateLimit-Daily-Remaining to throttle proactively.

Cache responses

Store and reuse data that doesn’t change frequently (brands, competitors, topics).

Batch and filter

Use query filters (provider, period, limit) to fetch only the data you need.

Retry logic

async function fetchWithRetry(url, options, maxRetries = 10) {
  for (let attempt = 0; attempt < maxRetries; attempt++) {
    const response = await fetch(url, options);

    if (response.status !== 429) return response;

    // Retry-After points at the blocking window
    // (minute or day window), not just the minute reset.
    const retryAfterSec = Number(response.headers.get('Retry-After') ?? '60');
    const waitMs = Math.max(retryAfterSec * 1000, 1000);

    const body = await response.clone().json().catch(() => ({}));
    console.warn(
      `Rate limited on ${body.limit ?? 'unknown'} window. Retrying in ${waitMs}ms...`
    );

    await new Promise((r) => setTimeout(r, waitMs));
  }

  throw new Error('Max retries exceeded');
}

If you see "limit": "daily" on retry, waiting within the same process rarely helps: the daily window can be hours away. Persist the X-RateLimit-Daily-Reset timestamp and reschedule the job instead of blocking a worker.

Reduce API usage

Use filtering parameters

Instead of fetching all data and filtering client-side, use query parameters:

# Fetch all answers, then filter in code
GET /api/v1/brands/{brandId}/answers

# Filter at the API level
GET /api/v1/brands/{brandId}/answers?provider=chatgpt&hasSelfMention=true&limit=50

Cache stable data

Cache data only for as long as your integration can tolerate staleness:

Brands list: changes when brand access changes
Competitors list: changes with configuration and observed data
Topics/Tags: changes when workspace configuration changes

Use date ranges

Limit data retrieval to relevant time periods:

# Bound an otherwise unbounded request to the last 7 days
GET /api/v1/brands/{brandId}/performance?period=7

Discuss higher limits

Contact team@qwairy.co with your use case and expected volume. Any change depends on the workload and account configuration.

Get started

Configure data

Monitor and measure

Analyze and act

Agency and automation

Implementation guides

Current limits

Rate-limit headers

Synthetic headers

Handle rate limits

Retry practices

Honor Retry-After

Watch both remaining headers

Cache responses

Batch and filter

Retry logic

Reduce API usage

Use filtering parameters

Cache stable data

Use date ranges

Discuss higher limits

​Current limits

​Rate-limit headers

​Synthetic headers

​Handle rate limits

​Retry practices

Honor Retry-After

Watch both remaining headers

Cache responses

Batch and filter

​Retry logic

​Reduce API usage

​Use filtering parameters

​Cache stable data

​Use date ranges

​Discuss higher limits

Current limits

Rate-limit headers

Synthetic headers

Handle rate limits

Retry practices

Retry logic

Reduce API usage

Use filtering parameters

Cache stable data

Use date ranges

Discuss higher limits