Restful Booker is a small hotel-booking API made specifically for people learning API testing. Its documented surface is a booking resource with create, read, update, partial update and delete, an /auth endpoint that issues a token, and a /ping health check. Updates and deletes need that token as a cookie or an HTTP Basic header, and its documentation shows JSON, XML and form-encoded request bodies.
At a glance
Restful Booker compared with this playground, checked 2026-10-30.
Restful Booker
Fun API Playground
Main purpose
API testing practice on a booking API
API testing practice across 55 APIs
Auth
Token from /auth as a cookie, or HTTP Basic, for PUT/PATCH/DELETE
Bearer roles, signed JWTs, OAuth 2.0 flows
Isolation
One shared public instance
Isolated sandbox per X-Sandbox-ID; browser mode is local
Concurrency, idempotency, rate limits
Not documented
ETag/If-Match 412, Idempotency-Key, 429 with Retry-After
Self-hosting
Docker Compose
Not packaged for self-hosting
Request body formats
JSON, XML and form-encoded
JSON-first; see each endpoint
Where it stops
It is one domain on one shared public instance, so what you can rehearse is the booking lifecycle and the token step around it. Concurrency control, idempotency, rate limiting, webhooks and most of the 4xx and 5xx range are outside its documented scope.
What is different here
Fun API keeps the same no-signup starting point but spreads the practice over 55 APIs: Bearer roles that produce a 403, signed JWTs and OAuth 2.0 flows, ETag and If-Match with a real 412, Idempotency-Key replay, rate limits with Retry-After, webhooks with HMAC signatures, and guided challenges that check the response you actually produced. Live requests are isolated per X-Sandbox-ID, and browser mode runs without the network.
What Restful Booker does better
A long-standing teaching staple: many API testing courses and articles already use it, so exercises written for it are easy to find.
Self-hostable with Docker Compose from its public repository.
Accepts XML and form-encoded bodies as well as JSON, which is useful when a course covers request body formats.
What this playground does better
Many domains and 509 endpoints instead of one booking resource.
Error paths with a cause behind them: 409, 412, 415, 422, 429 and 503 among them.
Per-caller sandboxes on the live API, so another learner cannot change your data mid-test.
Interactive docs with Try it out, OpenAPI 3.1 and Postman exports, and generated code in nine languages.
Which to use
Use Restful Booker when a course or exercise you follow is written for it, or when you need XML bodies. Use Fun API when you want to practise the failure modes around auth, concurrency, retries and webhooks without sharing data with other learners.
Checked against Restful Booker as of 2026-10-30.
Official sources and scope
This compares a training playground with the documented use case of the other tool. Plans, limits and hosted features can change. For current terms, use the official sources below.
JSONPlaceholder — JSONPlaceholder fakes its writes. If you need a POST that a later GET can find, that is the difference.
httpbin — httpbin shows you the request. This shows you an API. They answer different questions.
ReqRes — Choose between a hosted test backend with account-backed collections and a no-signup training playground with themed scenarios.
json-server — json-server turns a JSON file into a REST API in seconds. It does not push back — and that is the difference.
WireMock — WireMock reproduces the API you already know, exactly. This one gives you an API you do not control.
Mockoon — Mockoon is for designing your own mock API. This one is an API already designed, with rules you have to discover.
Beeceptor — Beeceptor gives you a hosted endpoint to inspect and mock. This gives you finished APIs that behave like real ones.
DummyJSON — DummyJSON has rich sample data and a JWT login. Its writes are simulated; here they persist.
Postman mock servers — A Postman mock server replays the examples saved in a collection. This one runs an API with state and rules.
PokeAPI — PokeAPI is the real Pokémon database, read-only. This Pokémon API is invented data you can write to and break.
SWAPI — SWAPI serves Star Wars data, read-only. This Star Wars API is invented practice data you can change.
Swagger Petstore — Petstore is the reference sample for an OpenAPI document. This is a set of APIs whose behaviour is the thing you test.
GoRest — GoRest needs a token from a social login before you can write. This needs no account at all.
FakeStoreAPI — FakeStoreAPI returns a fake id for your POST and saves nothing. Here the cart, coupon and checkout keep their state.
Practice Software Testing — Toolshop is a full web shop with seeded bugs for UI and API testing. Fun API is many small APIs built around HTTP behaviour.
balldontlie — balldontlie serves real league data behind an API key and a free tier of a few requests a minute. This serves invented leagues you can drive yourself.
the HAPI FHIR public test server — The HAPI public server is a full FHIR implementation shared by everyone and purged regularly. This is a small, isolated, synthetic subset for practising tests.
the National Weather Service API — api.weather.gov is real, free US government weather data. This is a deterministic weather API for tests that need the same forecast every time.
local LLM mock servers — mockllm, llmock and similar packages run a fake OpenAI/Anthropic server on your machine. This is the same idea, hosted, with failure scenarios chosen by model name.
the free mock API landscape — Six free options, what each is genuinely for, and how to tell which one your problem needs.