Skip to main content
Back to Dev generators

Dev

HTTP Status Code Explainer

Used by developers, writers, and creators worldwide.

An HTTP status code explainer takes a status code and explains it in depth — its meaning, when to use it, and a concrete example. Status codes are how the web signals success, redirection, and error, and choosing the right one makes an API clear and correct. This tool goes beyond a one-line definition: it tells you what a code means, the situation it is meant for, and an example of when you would return it, so you build genuine intuition. Filter by class to focus on 2xx successes, 3xx redirects, 4xx client errors, or 5xx server errors. It is a study aid for learners and a quick reference when you are designing API responses.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Choose a status class, or leave it on any.
  2. Click Generate to get a code with a full explanation.
  3. Read the meaning, when to use it, and the example.
  4. Generate again to learn more codes or pick the right one.

Use Cases

  • •Choosing the right status code for an API response
  • •Learning what each status code means in depth
  • •Quiz and revision practice for web development
  • •Settling a debate about which code to return
  • •Documentation that explains status meanings accurately

Tips

  • →Use the most specific accurate code — 201 for creation, not just 200.
  • →Remember 401 is about authentication and 403 is about authorisation.
  • →Return 429 with a Retry-After header when rate-limiting clients.
  • →Reserve 5xx for genuine server faults, not client mistakes.

FAQ

what is the difference between 401 and 403

401 Unauthorized means authentication is missing or failed — the server does not know who you are. 403 Forbidden means you are authenticated but lack permission for this resource. In short, 401 is about identity and 403 is about authorisation.

when should i return 201 instead of 200

Return 201 Created when a request successfully creates a new resource, typically including the new resource's location. Use 200 OK for a successful request that does not create something new, such as a GET or an update that returns the result.

what does 429 mean

429 Too Many Requests signals that a client has exceeded a rate limit. APIs return it to protect against abuse or overload, usually with a Retry-After header telling the client when it may try again. Handling it gracefully is important for any API client.