Skip to main content
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
  • 150,000 requests per week
Each window starts with your first request and resets one full period later; the weekly window is a rolling 7 days, not a calendar week. 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 limits than the default quotas, including:
  • Reporting: /v3/reporting/*
  • Sequence statistics:
    • /v3/sequences/{id}/stats
    • /v3/sequences/stats
  • Support requests:
    • /v3/support/*
    • POST /v3/support/requests
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
  • Body:
The numbers in detail reflect the limit that was exceeded, for example 3000 per 1h for the hourly quota or 150000 per 7d for the weekly one.

Response headers

Successful responses include headers describing your current quota: These headers are not included on 429 responses, which carry only Retry-After.
The headers report the longest-period limit that applies to the endpoint. A shorter limit, such as the per-minute quota, can return 429 while x-rate-limit-remaining still shows requests left, so don’t rely on these headers to predict a 429.

Check your usage

GET /v3/rate-limits returns every limit that applies to you — per minute, per hour and per week — with how many requests you have used and when each count resets, in one call. The response headers cover only one limit.

Raise your limits

API limit packages raise your limits. Each active package adds the standard limits once more, for you alone: with 2 active packages you get 300 requests per minute, 9,000 per hour and 450,000 per week, and the stricter reporting limits triple the same way. Packages raise the limits on this page; the MCP server limits stay the same. Packages are bought for your organization and shared through one pool.
1

Buy packages

The organization owner buys them in the Reply app, in Plans & Billing, through the API limit packages item of the upgrade wizard. Packages can’t be bought through the API.
2

Claim them

Each user claims packages from the pool for their own limits, in API keys → API rate limit packages or with PUT /v3/settings/api-limit-packages/mine. New limits apply within about 30 seconds.
3

Check them

GET /v3/settings/api-limit-packages shows the pool and the packages you hold. GET /v3/rate-limits shows activePackages and the limit that applies to you in each window.

Handling 429

1

Respect Retry-After

Wait for the number of seconds specified in the Retry-After header before retrying the request.
2

Limit concurrency

For bulk operations, process requests sequentially or use a small concurrency limit instead of sending many requests in parallel.
3

Raise your limits if 429s keep coming

If normal use keeps hitting a limit, claim packages from your organization’s pool, or ask the organization owner to buy more. See Raise your limits.