Guess the HTTP status: 20 everyday situations
Checkcraft is a desktop app for checking APIs and logs without code, with a free edition. Download, no sign-up →
A guard will not let you in without a pass: is that 401 or 403? The café moved for good: 301 or 302? Twenty everyday situations, four answers each and a short explanation after every one. The last question has a twist.
Why a tester should care
The status code is the first thing an automated test sees and the most common thing it checks. But a status only tells you how the server understood the request. It does not tell you whether the result is right: a server can honestly answer 200 and return a wrong total. So after the game, try the practice API where every response is 200 and ten bugs hide inside.
How to remember the groups
1xx are informational, 2xx mean the request succeeded, 3xx say go elsewhere, 4xx are the asker’s mistake, 5xx are the server’s. 401 means "we do not know who you are", 403 means "we know, but no". 502: a gateway got an invalid answer from the next server; 504: it did not get one in time.
Repeat this on your own API
Checkcraft is a desktop app that saves API response checks without code and shows what did not match. Start with a sample, then use your own sanitized data. Free runs on Windows and Linux with no time limit.
Download FreeDownload and first runNo sign-up or email needed, the archive is ready in a couple of minutes. See the edition limits.
References
RFC 9110: HTTP status codes · MDN: HTTP response status codes
Start with the linked example and compare its result with your own test requirement.