ReqRes · Rate Limits

Reqres Rate Limits

ReqRes enforces per-plan request-rate quotas as of the 2025 relaunch. The /api/* and /app/* surfaces are scoped to an API key (free signup) and metered by daily request count per plan (250/day Free, 1000/day Lite, 100K/day Team). The /agent/v1/* Agent Sandbox is open in v1 with IP-based rate limiting; the paid Agent Developer plan raises the ceiling to 10M requests/month. Exceeding a plan budget returns 429 Too Many Requests. ReqRes has not publicly documented a per-second burst rate or specific retry-after headers; consumers should treat the daily quota as the primary limit and apply exponential backoff with jitter on 429 responses.

Reqres Rate Limits is the machine-readable rate-limit profile for ReqRes on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests_per_day, requests_per_month, and varies.

The profile also includes 6 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, unauthorized, and forbidden.

Tagged areas include Rate Limiting, Development, Fake API, and Agent Sandbox.

5 Limits Throttle: 429 Quota: 429
Rate LimitingDevelopmentFake APIAgent Sandbox

Limits

Free plan — daily requests key
requests_per_day · day
250
The Free plan caps total /api/* and /app/* requests at 250 per day per API key. Exceeding the cap returns 429 until the daily window resets.
Lite plan — daily requests key
requests_per_day · day
1000
$5/month Lite plan raises the daily ceiling to 1000 requests per key.
Team plan — daily requests account
requests_per_day · day
100000
$79/month Team plan provides 100K requests/day shared across the team account, with scoped per-engineer API keys for usage tracking.
Agent Developer — monthly requests key
requests_per_month · month
10000000
$49/month Agent Developer plan provides 10M requests/month against /agent/v1/* with all 15 deliberate failure scenarios unlocked.
Agent Sandbox v1 — open IP rate limit IP
varies
undisclosed per-IP cap on /agent/v1/* without an Agent Developer key
/agent/v1/* is open in v1 and falls back to IP-based rate limiting when no Agent Developer API key is present. The exact per-IP threshold is not published; treat the endpoint as best-effort without a key.

Policies

API key required on /api/* and /app/*
Every request to /api/* and /app/* must include an x-api-key header. Missing or invalid keys return 401. Sign up at app.reqres.in to get a free key.
Session bearer on /app/*
/app/* endpoints additionally require a per-user session bearer token (Authorization: Bearer ) obtained via POST /api/app-users/login. The session bearer carries per-user isolation.
Exponential backoff on 429
On 429 Too Many Requests, back off with exponential delay and jitter and respect the Retry-After header when present. Do not loop tight retries that will compound the quota burn.
Quotas are per UTC day
Daily quotas reset at the start of a new UTC day; plan rollover happens monthly on the billing anniversary.
Deliberate Agent Sandbox failures
The /agent/v1/scenarios surface intentionally returns failure responses (timeouts, malformed payloads, edge-case pagination cursors) so agents can be tested against realistic upstream conditions. These responses are not bugs and should not be retried blindly.
Writes are persisted only on collections/app-users
Legacy /api/users, /api/login, /api/register, /api/logout endpoints simulate success but do not persist. Persistent state lives in /api/collections/* and /api/app-users/* (paid plans add custom schemas and webhooks on data changes).

Sources