How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
ReqRes

ReqRes Legacy API

The Legacy API from ReqRes — 4 operation(s) for legacy.

Documentation Provider Profile APIs.io OpenAPI GitHub

ReqRes Legacy API is one of 6 APIs that ReqRes publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 16 JSON Schema definitions.

Tagged areas include Legacy. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, pricing, an engineering blog, a JSON-LD context, and 16 JSON Schemas.

This API exposes 8 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 2.1.0.

Requests are made against 2 base URLs: https://reqres.in, http://localhost:8000.

8 operations 4 paths 9 schemas 1 DELETE4 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.1.0
Base URL
https://reqres.in/
Authentication
API Key, HTTP Bearer
Contact
ReqRes Support
License
MIT
Resource Areas
1

Authentication & Security 2

ReqRes Legacy API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). It accepts HTTP bearer tokens (session_token) (BearerAuth).

Paths & Operations 8

Across 4 paths, the API surfaces 8 operations — 1 DELETE, 4 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Legacy 8
GET
/api/users
ReqRes List Users (legacy)
getLegacyUsers 2 params → 200400
POST
/api/users
ReqRes Create User (legacy)
createLegacyUser body → 201400
GET
/api/users/{id}
ReqRes Get User by Id (legacy)
getLegacyUserById 1 param → 200404
PUT
/api/users/{id}
ReqRes Update User (legacy)
updateLegacyUser 1 param body → 200400
PATCH
/api/users/{id}
ReqRes Patch User (legacy)
patchLegacyUser 1 param body → 200400
DELETE
/api/users/{id}
ReqRes Delete User (legacy)
deleteLegacyUser 1 param → 204
GET
/api/unknown
ReqRes List Resources (legacy)
getLegacyUnknown 2 params → 200400
GET
/api/unknown/{id}
ReqRes Get Resource by Id (legacy)
getLegacyUnknownById 1 param → 200404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are LegacyUnknownListResponse (6 properties), LegacyUserListResponse (6 properties), LegacyUnknown (5 properties), LegacyUser (5 properties). Each schema is shown below with its type and property counts.

LegacyUnknownListResponse
object
6 properties 5 required
ErrorResponse
object
2 properties 1 required
LegacyMutationResponse
object
3 properties
LegacyUnknown
object
5 properties 5 required
LegacyUserResponse
object
2 properties 1 required
LegacyMutationRequest
object
LegacyUserListResponse
object
6 properties 5 required
LegacyUnknownResponse
object
2 properties 1 required
LegacyUser
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

reqres-legacy-api-openapi.yml Raw ↑

Other APIs ReqRes publishes across the network.

ReqRes Agent Sandbox API
AE Profile APIs.io
ReqRes App Users API
AE Profile APIs.io
ReqRes Authentication API
AE Profile APIs.io
ReqRes Collections API
AE Profile APIs.io
ReqRes Custom Endpoints API
AE Profile APIs.io
#Legacy
← Back to R APIs
API Details
ID
reqres:reqres-legacy-api
Base URL
https://reqres.in/
Docs
https://reqres.in/
Provider
ReqRes
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=reqres-legacy-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/reqres-legacy-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of ReqRes Legacy API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.