The Office API — free mock REST API for testing

Employees, office pranks and quotes from a fictional paper company mockumentary. Practice CRUD, Bearer auth, nested resources, pagination and optimistic concurrency.

The Office API covers a paper company: employees, the pranks played on them and a quote collection. It is one of the gentler CRUD surfaces in the catalog and a reasonable first target when you are teaching someone the request/response loop before introducing auth, concurrency or error injection.

Base URL: https://funapi.dev/api/office/v1 · 8 endpoints · OpenAPI 3.1 spec and Postman collection available. New here? Read the getting started guide.

Example request and response

GET https://funapi.dev/api/office/v1/employees — List employees (paginated, filter by department). No token, no signup:

curl -i https://funapi.dev/api/office/v1/employees

answers 200 OK with:

{
  "page": 1,
  "pageSize": 4,
  "total": 8,
  "totalPages": 2,
  "data": [
    {
      "id": 1,
      "name": "Michael Scott",
      "role": "Regional Manager",
      "department": "Management",
      "deskNumber": 1,
      "_v": 1
    },
    {
      "id": 2,
      "name": "Dwight Schrute",
      "role": "Assistant to the Regional Manager",
      "department": "Sales",
      "deskNumber": 2,
      "_v": 1
    },
    {
      "id": 3,
      "name": "Jim Halpert",
      "role": "Sales Representative",
      "department": "Sales",
      "deskNumber": 3,
      "_v": 1
    },
    {
      "id": 4,
      "name": "Pam Beesly",
      "role": "Receptionist",
      "department": "Reception",
      "deskNumber": 4,
      "_v": 1
    }
  ]
}

Open and run this endpoint

What you can practise here

• Create, read, update and delete an employee end to end, watching the status code change at each step.
• Repeat the delete and see the 404 that tells you the resource is already gone.
• Filter pranks by target and confirm an unmatched filter is an empty 200, not an error.
• Attempt a write without a token to meet the 401 before you meet it in production.

employees

eight desks, one regional manager

• GET /office/v1/employees — List employees (paginated, filter by department) · Responds with 200 400 404 Link to this endpoint
• GET /office/v1/employees/{id} — Get one employee · Responds with 200 404 Link to this endpoint
• GET /office/v1/employees/{id}/pranks — Get pranks involving an employee (nested resource) · Responds with 200 404 Link to this endpoint
• POST /office/v1/employees — Hire a new employee (requires Bearer auth) · Responds with 201 400 401 Link to this endpoint
• PUT /office/v1/employees/{id} — Update an employee (requires Bearer auth) · Responds with 200 400 401 404 412 Link to this endpoint
• DELETE /office/v1/employees/{id} — Fire an employee (requires Bearer auth) · Responds with 204 401 403 404 412 Link to this endpoint

pranks

mostly aimed at one assistant (to the) regional manager

• GET /office/v1/pranks — List pranks, filter by severity · Responds with 200 400 Link to this endpoint

quotes

that's what she said

• GET /office/v1/quotes/random — A random quote · Responds with 200 Link to this endpoint

Related APIs

• Friends API — Characters, episodes & quotes from the coffee-house gang.
• Movies API — QA-themed cinema. Sort, filter, rate.
• Harry Potter API — Houses, students & spells from a magic school.
• Star Wars API — Characters, planets & starships from a galaxy far away.

All 39 mock REST APIs

Use this response elsewhere

• JSON to TypeScript on fundata.dev — an interface for this response
• JSON to Zod on fundata.dev — a runtime validator for it
• mock API data on fundata.dev — thousands of records of the same shape for your own fixtures

Unofficial and fan-made. The The Office API is a practice API that borrows a theme; it is not affiliated with, sponsored or endorsed by the owners of the names it references, which belong to them. Every record it returns is test data for exercising HTTP behaviour, not an authoritative source on the subject.

Last updated 2 October 2026