Skip to main content
The Reply API enforces per-user request quotas. Exceeding a quota returns 429 Too Many Requests.

​
Limits

  • 100 requests per minute
  • 3,000 requests per hour
Quotas are scoped per user. Requests from all processes acting on behalf of the same user share the same counter.

​
Stricter endpoints

Some endpoints enforce tighter hourly caps than the general limits — for example:
  • Reporting — /v3/reporting/*
  • Sequence statistics — /v3/sequences/{id}/stats, /v3/sequences/stats
Space heavy analytics queries out and expect 429 sooner than the general limits imply.

​
The 429 response

When a quota 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

1

Respect Retry-After

Wait the number of seconds indicated by the Retry-After header before retrying the same request.
2

Serialize bulk work

Process bulk operations sequentially or with a small concurrency limit rather than firing all requests in parallel.