Pick one and press Start, then click Next › to step through it.
Watch for
The repeat GET coming back 304 with no body resent, and the 503 recovering on retry — caching and safe retries in action.
More about this scenario
You'll learn
What the major HTTP status classes mean and when each one shows up in a real API.
How it runs
A GET returns 200 and caches with an ETag; a repeat GET revalidates to 304; a POST creates a resource (201); a GET to a bad path is 404; a flaky endpoint 503s once, then an idempotent retry succeeds with 200.