Coffee Shop API — free mock REST API for testing

A café counter API: browse drinks, place orders — and GET /teapot, which proudly returns HTTP 418 "I'm a teapot".

The Coffee Shop API is the catalog's rate-limiting playground and the home of HTTP 418. Its rush endpoint enforces a real quota: exceed it and you get a 429 with Retry-After and the usual X-RateLimit headers, refreshed on a live window. Client-side throttling and backoff are almost impossible to test against a well-behaved API, and this one misbehaves on request.

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

What you can practise here

• Fire requests at the rush endpoint until it answers 429, then respect Retry-After and watch the window reopen.
• Read X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset on a successful call and build your throttle from them.
• Ask the teapot endpoint to brew coffee and collect the 418 your status-code assertion table is missing.
• Order a drink that is out of stock and separate the 409 from the 400 in your error handling.

drinks

hot and cold

• GET /coffee/v1/drinks — List drinks, filter by type
• GET /coffee/v1/drinks/{id} — Get one drink

orders

name on the cup

• POST /coffee/v1/orders — Order a drink
• PUT /coffee/v1/orders/{id}/ready — Mark an order ready (409 if already ready)

rush

hammer it and watch the 429s

• GET /coffee/v1/rush-hour — Rush hour special — max 3 requests per 10s

teapot

RFC 2324 compliance

• GET /coffee/v1/teapot — Try to brew coffee in a teapot

Related APIs

• Pizza Orders API — Place & track orders. Includes a guaranteed 500.
• Football API — Teams, squads, standings & simulated matches.
• Bank API — Accounts, transfers & cursor pagination. Home of the 402.
• Airline API — Flights, seat conflicts & overbooking drama.

All 39 mock REST APIs