ReqRes
ReqRes (reqres.in) is a hosted REST API originally launched by Ben Howdle as a free no-auth fake-API surface for AJAX prototyping, tutorials, and frontend testing. As of the 2025 relaunch it operates as a freemium SaaS product: every request to /api/* and /app/* now requires an x-api-key header obtained via free signup at app.reqres.in, while the /agent/v1/* Agent Sandbox is open in v1 with IP-based rate limiting. The legacy demo surface (/api/users, /api/login, /api/register, /api/unknown, delayed responses) continues to return the same fixture payloads it always has — what changed is the API-key gate and the addition of persistent collections, app users, custom endpoints, and an agent-targeted sandbox with deliberate failure scenarios. ReqRes remains the default fake-API endpoint cited in countless React, Vue, Angular, and bootcamp tutorials.
APIs
ReqRes API
Hosted REST surface spanning six business areas — Legacy demo data, Authentication simulation, Collections (persistent), App Users (sessions), Custom Endpoints, and the Agent Sa...
Collections
ReqRes API
OPENPricing Plans
Rate Limits
Features
Stable /api/users, /api/users/{id}, /api/unknown, /api/unknown/{id} fixture data preserved from the original reqres.in launch — the same payloads tutorials have been wired against for years.
/api/register, /api/login, and /api/logout return success-shaped tokens without creating real accounts — drop-in for teaching auth patterns without standing up a real identity provider.
/api/collections/{slug}/records supports GET/POST/PUT/DELETE with real persistence on paid plans, with custom schemas on the Dev tier and above.
/app/* surface lets each app user authenticate independently with a session bearer, so client-side prototypes can model real per-user isolation.
/api/custom/{path} executes user-defined endpoints, letting builders shape arbitrary REST surfaces without writing backend code.
/agent/v1/* exposes endpoints designed for AI coding agents — cursor pagination, deeply nested resources, deliberate failure scenarios, and deterministic seeded fixtures.
The Agent Developer plan unlocks 15 failure scenarios on /agent/v1/scenarios so AI agents can be tested against timeouts, rate limits, validation errors, and pagination edge cases.
Legacy endpoints accept a ?delay=N query param to simulate slow upstream conditions — useful for spinner/loading-state testing.
Served exclusively over HTTPS at reqres.in.
All origins are allowed, making ReqRes safe to call directly from browser-based prototypes.
Use Cases
The default fake API cited in React, Vue, Angular, and Svelte tutorials when an author needs a real HTTP endpoint without standing up a backend.
Coding bootcamps wire exercises against ReqRes legacy endpoints so students can practice CRUD flows on a stable, free, no-signup surface.
Use the legacy and Collections surfaces to exercise HTTP client libraries (fetch, axios, requests, OkHttp) against a real REST API.
Build a UI against persistent ReqRes collections before standing up a real backend; swap in a real API later by renaming the base URL.
Test AI coding agents against the /agent/v1/* sandbox — cursor pagination, deliberate failures, deterministic seeded fixtures.
Power live sales demos for tools that need to talk to an API without exposing customer data.
Hands-on workshops where every participant needs a working API endpoint in under a minute.
Integrations
Public Postman collections wrap ReqRes endpoints for quick HTTP exploration and learning.
Frequently used as the default example endpoint in HTTP clients including Hoppscotch and Insomnia.
Often paired with MSW so frontend tests can intercept and stub ReqRes traffic deterministically.
The /agent/v1/* sandbox is purpose-built for AI coding agents like Claude Code, with deliberate failure scenarios and cursor pagination.
Browser E2E test suites use ReqRes as a stable upstream when writing tests that depend on real network traffic.
Solutions
From $499/year per team, deploy ReqRes inside your own infrastructure with no external dependencies — useful for regulated environments that can't call a public service.
On the Team plan, issue scoped API keys per engineer with usage tracking, so a single project can attribute spend back to individuals.
On the Pro plan, configure webhooks that fire on collection data changes, letting ReqRes drive downstream pipelines as a prototyping backend.