A National Weather Service API alternative for testing
The National Weather Service API at api.weather.gov serves real forecasts, observations and alerts as open data, free of charge and without an API key. Its documentation asks every client to send a User-Agent that identifies the application, and says rate limits exist but are not published.
At a glance
the National Weather Service API compared with this playground, checked 2026-11-09.
the National Weather Service API
Fun API Playground
Data
Real US weather
Synthetic, deterministic
Access
No key; User-Agent required
No key
Rate limits
Exist, not published
Abuse protection only
Failure testing
Only when the service actually fails
scenario=outage, timeout, stale
Units
Per product
units=us or si
Where it stops
Real weather is exactly what a test does not want: the forecast changes every hour, an alert exists only when weather does, and an outage cannot be produced on demand. Forecasts also take two calls — /points for the grid, then the gridpoint forecast — which is right for production and extra setup for a tutorial.
What is different here
The Weather API here returns synthetic, deterministic conditions, daily and hourly forecasts and state alerts for a fixed set of locations, in °F/mph or °C/km/h. A scenario parameter turns on a 503 with Retry-After, a slow 504 or a stale response with a Warning header, so the failure paths can be tested as easily as the happy one.
What the National Weather Service API does better
Real forecasts, observations and official alerts — the source of truth for US weather.
Free, open government data with no key.
Rich products: gridpoint data, stations, radar and alert details.
What this playground does better
The same request returns the same forecast, so tests can assert values.
Outage, timeout and stale-data scenarios on demand.
One call per forecast, with US or metric units chosen by a parameter.
Locations outside the US included.
Which to use
Use api.weather.gov for real weather in a real product. Use this API in tutorials and tests where the answer must not change and the failures must be reproducible.
Checked against the National Weather Service API 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 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.
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.