Your app's real endpoints, with believable records behind every list — and the chaos controls work on them, so you can see what your app does when its own API answers 503, times out, or fails one request in three. OpenAPI 3 or Swagger 2.0, as JSON.
Already have the data you want served? Use your own data instead — it serves exactly what you paste.
Expires . This page keeps it until then — refresh, or come back later, and it will still be here. Export it below if you want it for longer; that file runs on your machine and never expires.
| Resource | Records | URL |
|---|
This is the part no other mock service does — your data, failing how you ask.
A hosted mock is useful until it expires, nine days at most. These files run offline, in CI, and long after this service is gone.
# one file, no install, no network — and the chaos controls still work node mock-server.mjs python3 mock_server.py java MockServer.java dotnet run MockServer.cs # then, on your own machine: curl 'http://localhost:4000/customers?_status=503' curl 'http://localhost:4000/customers?_fail_rate=0.3'
All four servers are self-contained: your data is embedded in the file and
parsed at startup, so there is nothing to install and nothing to fetch — no
npm, no pip, no Maven, no NuGet. They answer identically, byte for byte, so
the language is a preference and not a compromise.
They carry the same controls as the hosted API, which is the
part json-server cannot do — it will serve db.json
happily, but it cannot fail on demand.