# ReqRes - Backend platform for frontend developers

> ReqRes is a backend you call with fetch(). Collections, auth, logs, and automations. No servers to run.

## For LLMs building against ReqRes

Full API reference (JSON): https://reqres.in/llm.json
Full API reference (text): https://reqres.in/llm.txt
OpenAPI spec: https://reqres.in/openapi.json

## Quick context

ReqRes has two API surfaces:

1. Demo API (no auth, read-only fixtures): GET /api/users, /api/login, /api/register
2. Project API (auth required, persistent CRUD): /api/collections/{slug}/records

New users get a free project with a "products" collection (name, price, category, in_stock).

## Auth patterns

- Demo endpoints: no auth needed
- Project reads: x-api-key header (public key, pub_* prefix, browser-safe)
- Project writes: x-api-key header (manage key, pro_* prefix, server-side only)
- App user endpoints: Authorization: Bearer <session_token> (from magic link flow)

## Critical: request body format

POST and PUT to /api/collections/* require the body wrapped in a "data" object:

  {"data": {"name": "Example", "price": 9.99}}

Sending fields at the top level without "data" returns 400.

## Plans

- Free: $0/mo, 250 req/day, 3 collections, 100 records
- Lite: $5/mo, 1,000 req/day
- Dev: $12/mo, 5,000 req/day, 5 collections, 5,000 records, app users
- Pro: $29/mo, 25,000 req/day, 20 collections, 50,000 records

## Links

- Sign up: https://app.reqres.in
- Docs: https://reqres.in/docs
- Example app (source): https://github.com/benhowdle89/reqres-demo-app
- Blog: https://reqres.in/blog