A FakeStoreAPI alternative where the cart remembers
FakeStoreAPI is a free e-commerce sample API with products, carts and users, category filters, sorting and limits, and a login endpoint. It is a popular backing API for front-end store demos and tutorials, and its source is public under the MIT licence.
At a glance
FakeStoreAPI compared with this playground, checked 2026-10-30.
FakeStoreAPI
Fun API Playground
Writes persist
No: POST returns a fake id, updates and deletes are not saved
Its README is explicit that writes are simulated: a POST returns a new id without inserting anything, and updates and deletes do not change the database. That is fine for rendering a shop, and it means a test cannot create a cart and then read it back.
What is different here
The Shop API here persists inside your sandbox: build a cart, apply a coupon, hit an out-of-stock conflict and check out, then read the order back. Around it are an idempotent checkout, Bearer roles, rate limits and the rest of the catalog, with OpenAPI and Postman exports for every API.
What FakeStoreAPI does better
Product data with images and categories that looks right in a store UI out of the box.
A small, memorable surface that many front-end tutorials already use.
Open source under MIT, so the data and server can be studied or reused.
What this playground does better
Writes persist, so create-then-read and multi-step checkout flows are testable.
Business-rule failures: out-of-stock conflicts, invalid coupons and idempotent checkout retries.
Across the rest of the catalog, auth with roles that produce 401 and 403 on purpose.
Guided challenges and per-caller sandboxes on the live API.
Which to use
Use FakeStoreAPI to fill a store front-end with plausible products. Use Fun API when you need to test what happens across a checkout: state, conflicts and retries.
Checked against FakeStoreAPI 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.
GoRest — GoRest needs a token from a social login before you can write. This needs no account at all.
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.