ReqRes

A hosted fake REST API for testing: page through sample users and colors, and send creates, updates, deletes, sign-ups and log-ins that answer like a real API but store nothing. Good for trying out a workflow's loops and error handling. No account or API key required.

Actions

Action	What it does
Create user	Send a new user to ReqRes, which answers like a real API: with a new id and a creation time.
Delete user	Send a delete for a user to ReqRes, which answers 204 No Content like a real API.
Get color	Get one of ReqRes's sample colors by id: its name, year, hex code and Pantone number.
Get user	Get one of ReqRes's sample users by id: name, email and avatar.
List colors	List a page of ReqRes's 12 sample colors (its 'unknown' resource): Pantone colors of the year with name, year, hex code and Pantone number.
List users	List a page of ReqRes's 12 sample users, with name, email and avatar, plus the paging details.
Log in	Log in as one of ReqRes's sample users and get back a made-up token.
Register	Register one of ReqRes's sample users and get back their id and a made-up token.
Update user	Send a new name or job for a user to ReqRes, as a PUT or a PATCH, and get back what was sent with an update time.

Create user

Send a new user to ReqRes, which answers like a real API: with a new id and a creation time. ReqRes stores nothing, so this is safe to run as often as you like. No API key required.

Inputs

NamenametextRequired: The new user's name.
Jobjobtext: The new user's job.

Outputs

created_attext: When ReqRes answered, as an ISO 8601 time.
idtext: The id ReqRes gave the new user, e.g. '941'. It is made up for the answer: the user is not stored.
jobtext: The job sent, if any.
nametext: The name sent.

Example output

{
  "created_at": "2026-10-16T18:44:26.271Z",
  "id": "941",
  "job": "leader",
  "name": "morpheus"
}

Delete user

Send a delete for a user to ReqRes, which answers 204 No Content like a real API. ReqRes stores nothing, so this is safe to run as often as you like. No API key required.

Inputs

User idreqres_user_idnumberRequired: The sample user's id, 1 to 12.At least 1.

Outputs

deletedtrue/false: True when ReqRes accepted the delete (HTTP 204).
status_codenumber: The HTTP status ReqRes answered with, 204 on success.
user_idnumber: The id of the user deleted.

Example output

{
  "deleted": true,
  "status_code": 204,
  "user_id": 2
}

Get color

Get one of ReqRes's sample colors by id: its name, year, hex code and Pantone number. No API key required.

Inputs

Color idcolor_idnumberRequired: The sample color's id, 1 to 12.At least 1.

Outputs

colorobject: A ReqRes sample color (its 'unknown' resource).

Example output

{
  "color": {
    "hex": "#C74375",
    "id": 2,
    "name": "fuchsia rose",
    "pantone_value": "17-2031",
    "year": 2001
  }
}

Get user

Get one of ReqRes's sample users by id: name, email and avatar. An id above 12 fails with 'not found', which is handy for testing error handling. No API key required.

Inputs

User idreqres_user_idnumberRequired: The sample user's id, 1 to 12.At least 1.

Outputs

userobject: A ReqRes sample user.

Example output

{
  "user": {
    "avatar_url": "https://reqres.in/img/faces/2-image.jpg",
    "email": "janet.weaver@reqres.in",
    "first_name": "Janet",
    "full_name": "Janet Weaver",
    "id": 2,
    "last_name": "Weaver"
  }
}

List colors

List a page of ReqRes's 12 sample colors (its 'unknown' resource): Pantone colors of the year with name, year, hex code and Pantone number. No API key required.

Inputs

Pagepagenumber: Which page to return, starting at 1. Defaults to the first.At least 1.
Per pageper_pagenumber: How many colors to put on a page, 1 to 12. Defaults to 6.From 1 to 12.

Outputs

colorslist: The colors on this page.
countnumber: How many colors are on this page.
has_moretrue/false: True when a later page follows this one.
next_pagenumber: The next page's number, or null on the last page.
pagenumber: This page's number.
per_pagenumber: How many colors fit on a page.
totalnumber: How many colors there are in all.
total_pagesnumber: How many pages there are at this page size.

Example output

{
  "colors": [
    {
      "hex": "#C74375",
      "id": 2,
      "name": "fuchsia rose",
      "pantone_value": "17-2031",
      "year": 2001
    }
  ],
  "count": 1,
  "has_more": true,
  "next_page": 3,
  "page": 2,
  "per_page": 1,
  "total": 12,
  "total_pages": 12
}

List users

List a page of ReqRes's 12 sample users, with name, email and avatar, plus the paging details. Handy for testing a loop over pages. No API key required.

Inputs

Pagepagenumber: Which page to return, starting at 1. Defaults to the first.At least 1.
Per pageper_pagenumber: How many users to put on a page, 1 to 12. Defaults to 6.From 1 to 12.

Outputs

countnumber: How many users are on this page.
has_moretrue/false: True when a later page follows this one.
next_pagenumber: The next page's number, or null on the last page.
pagenumber: This page's number.
per_pagenumber: How many users fit on a page.
totalnumber: How many users there are in all.
total_pagesnumber: How many pages there are at this page size.
userslist: The users on this page.

Example output

{
  "count": 1,
  "has_more": true,
  "next_page": 3,
  "page": 2,
  "per_page": 1,
  "total": 12,
  "total_pages": 12,
  "users": [
    {
      "avatar_url": "https://reqres.in/img/faces/2-image.jpg",
      "email": "janet.weaver@reqres.in",
      "first_name": "Janet",
      "full_name": "Janet Weaver",
      "id": 2,
      "last_name": "Weaver"
    }
  ]
}

Log in

Log in as one of ReqRes's sample users and get back a made-up token. A missing password or an unknown address comes back with 'success' false and the reason, so you can test both outcomes. No API key required.

Inputs

EmailemailtextRequired: One of ReqRes's sample users' addresses, such as eve.holt@reqres.in. Any other address is refused, which is handy for testing a failure.
Passwordpasswordtext: Any made-up password; ReqRes only checks that one is given. Leave it empty to test a refusal. Never use a real password: this is a public test service.

Outputs

emailtext: The address sent.
errortext: Why ReqRes refused, e.g. 'Missing password', or null on success.
successtrue/false: True when ReqRes accepted the address and password. False when it refused them; the reason is in 'error'.
tokentext: The made-up token ReqRes returns, or null when refused.

Example output

{
  "email": "eve.holt@reqres.in",
  "error": null,
  "success": true,
  "token": "QpwL5tke4Pnpja7X4"
}

Register

Register one of ReqRes's sample users and get back their id and a made-up token. Any other address, or a missing password, comes back with 'success' false and the reason, so you can test both outcomes. No API key required.

Inputs

EmailemailtextRequired: One of ReqRes's sample users' addresses, such as eve.holt@reqres.in. Any other address is refused, which is handy for testing a failure.
Passwordpasswordtext: Any made-up password; ReqRes only checks that one is given. Leave it empty to test a refusal. Never use a real password: this is a public test service.

Outputs

emailtext: The address sent.
errortext: Why ReqRes refused, e.g. 'Missing password', or null on success.
idnumber: The sample user's id, or null when refused.
successtrue/false: True when ReqRes accepted the address and password. False when it refused them; the reason is in 'error'.
tokentext: The made-up token ReqRes returns, or null when refused.

Example output

{
  "email": "eve.holt@reqres.in",
  "error": null,
  "id": 4,
  "success": true,
  "token": "QpwL5tke4Pnpja7X4"
}

Update user

Send a new name or job for a user to ReqRes, as a PUT or a PATCH, and get back what was sent with an update time. ReqRes stores nothing, so this is safe to run as often as you like. No API key required.

Inputs

User idreqres_user_idnumberRequired: The sample user's id, 1 to 12.At least 1.
Namenametext: The user's new name. Give a name, a job or both.
Jobjobtext: The user's new job. Give a name, a job or both.
Methodupdate_methodtext: Send the update as a PUT (replace the user) or a PATCH (change only these fields). Defaults to PUT.One of: PUT (Replace (PUT)), PATCH (Update the given fields (PATCH)). Default: PUT.

Outputs

jobtext: The job sent, or null when only the name was sent.
nametext: The name sent, or null when only the job was sent.
update_methodtext: 'PUT' or 'PATCH': how the update was sent.
updated_attext: When ReqRes answered, as an ISO 8601 time.
user_idnumber: The id of the user updated.

Example output

{
  "job": "zion resident",
  "name": "morpheus",
  "update_method": "PUT",
  "updated_at": "2026-10-16T18:44:27.472Z",
  "user_id": 2
}

ActionsCopy Anchor Link

Create userCopy Anchor Link

Inputs

Outputs

Delete userCopy Anchor Link

Inputs

Outputs

Get colorCopy Anchor Link

Inputs

Outputs

Get userCopy Anchor Link

Inputs

Outputs

List colorsCopy Anchor Link

Inputs

Outputs

List usersCopy Anchor Link

Inputs

Outputs

Log inCopy Anchor Link

Inputs

Outputs

RegisterCopy Anchor Link

Inputs

Outputs

Update userCopy Anchor Link

Inputs

Outputs

On this page

Actions

Create user

Delete user

Get color

Get user

List colors

List users

Log in

Register

Update user