> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reply.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate limits

> Rate limits, 429 responses, and retry guidance.

The Reply API limits the number of requests each user can make. When a limit is exceeded, the API returns `429 Too Many Requests`.

## Limits

* **100 requests per minute**
* **3,000 requests per hour**

Limits are applied per user. Requests made by multiple applications, scripts, or services on behalf of the same user count toward the same quota.

## Stricter endpoints

Some endpoints have lower hourly limits than the default quotas, including:

* **Reporting:** `/v3/reporting/*`
* **Sequence statistics:**
  * `/v3/sequences/{id}/stats`
  * `/v3/sequences/stats`

Analytics and reporting endpoints may return `429 Too Many Requests` before the general limits are reached.

## The 429 response

When a rate limit is exceeded, the API returns:

* **Status:** `429 Too Many Requests`
* **Headers:**
  * `Retry-After: <seconds>` — seconds to wait before the quota window resets
  * `Content-Type: application/problem+json`

## Handling 429

<Steps>
  <Step title="Respect Retry-After">
    Wait for the number of seconds specified in the `Retry-After` header before retrying the request.
  </Step>

  <Step title="Limit concurrency">
    For bulk operations, process requests sequentially or use a small concurrency limit instead of sending many requests in parallel.
  </Step>
</Steps>