GoRest is a free fake REST API with users, posts, comments and todos linked the way a real application links them, including nested routes such as /users/{id}/posts. Reads are open. Writes need a Bearer token that you generate after signing in with Google, Microsoft or GitHub. Its data is wiped and reseeded every three hours, and responses carry X-RateLimit headers, with a 429 when the per-token limit is exceeded.
At a glance
GoRest compared with this playground, checked 2026-10-30.
GoRest
Fun API Playground
Write access
Bearer token after Google, Microsoft or GitHub sign-in
Documented demo tokens, no signup
Data lifetime
Wiped and reseeded every 3 hours
Sandbox cleanup after about 24 hours of inactivity; browser data resets on reload
Domain
Users, posts, comments, todos
55 APIs across business, protocol and themed domains
Rate limits
Per token, with X-RateLimit headers and 429
Scenario limits with 429 and Retry-After
Concurrency and idempotency
Not documented
ETag/If-Match 412 and Idempotency-Key replay
Where it stops
Writing anything starts with an account and a token, which is an extra step in a classroom and a credential to keep out of shared collections. The domain is a social-app model; behaviour such as conflicts, version checks, idempotency or webhooks is outside its documented scope.
What is different here
Fun API publishes its demo tokens in the docs on purpose: qa-admin-token writes, qa-viewer-token gets a 403 on DELETE, and anything else is a 401, so role testing needs no signup. Writes persist inside your own sandbox, and the catalog adds ETag concurrency, Idempotency-Key replay, rate limits with Retry-After, OAuth 2.0 flows and signed webhooks.
What GoRest does better
A realistic relational model of users, posts, comments and todos that suits CRUD and nested-resource exercises.
Real per-token rate limits with X-RateLimit headers, configurable per token.
Records you create are visible only to your token, without having to choose a sandbox identifier yourself.
What this playground does better
No account or social login: writes work with documented demo tokens.
Role behaviour to test: a viewer token that gets 403 where the admin token succeeds.
Stateful failures beyond 429: 409, 412, 415 and 422 with a cause.
Browser mode runs the whole engine locally, with no network at all.
Which to use
Use GoRest for a relational CRUD model with real per-token rate limits. Use Fun API when learners should write and test roles without creating an account, or when the exercise is about failure handling.
Checked against GoRest 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.
Restful Booker — Restful Booker is one booking API built for testing practice. This is 55 APIs with the failure paths built in.
Swagger Petstore — Petstore is the reference sample for an OpenAPI document. This is a set of APIs whose behaviour is the thing you test.
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.