A HAPI FHIR test server alternative for API testing practice
The public HAPI FHIR test server at hapi.fhir.org is the reference open-source FHIR server running in public, with a full R4 implementation — every resource type, search parameters, operations and validation. Its home page asks users not to store personal health information and says the server is regularly purged and reloaded with fixed test data.
At a glance
the HAPI FHIR public test server compared with this playground, checked 2026-11-09.
the HAPI FHIR public test server
Fun API Playground
Scope
Full FHIR R4 server
Patient, Observation, Encounter subset
Data
Shared by all users; purged and reloaded
Per-sandbox copy of synthetic data
Writes
Open
Bearer demo token (documented)
Conflicts
Server-dependent
If-Match → 412 OperationOutcome
Deleted resources
Server behaviour
410 Gone on read
Where it stops
It is shared. Every visitor reads and writes the same data, so a test that creates a Patient and searches for it can find someone else's record, and data a suite relies on can disappear in a purge. Community threads also report slowdowns when many people use it at once.
What is different here
The FHIR R4 Health Records API here is deliberately small: Patient, Observation with LOINC vitals, and Encounter. Each X-Sandbox-ID gets its own copy, so a test sees only its own writes. It returns searchset Bundles with next and previous links, versioned W/ ETags with If-Match, 410 after delete and OperationOutcome errors — the behaviours a client test needs — with synthetic data only.
What the HAPI FHIR public test server does better
A full FHIR R4 implementation: all resource types, rich search, operations and validation.
The reference behaviour of a widely deployed open-source server.
Other FHIR versions and endpoints alongside R4.
What this playground does better
Isolated per sandbox: your writes are only yours and are not wiped mid-run.
Deterministic synthetic seed data, so assertions on counts and values hold.
Focused on client-test behaviour: paging links, version conflicts, 410 Gone, OperationOutcome.
Runs in the browser too, with no network.
Which to use
Use the HAPI server to check conformance against a complete FHIR implementation. Use this API to practise and automate client tests that need isolated, repeatable data.
Checked against the HAPI FHIR public test server as of 2026-11-09.
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.
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 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.