HTTP status codes
Look up any standard status code — what it means and when you should actually use it in your API or web app.
~~~
Daily drivers
The handful you'll see in logs every week:
~~~
Search
Group
Results
No matching codes.
| Code | Name | Meaning | When to use |
|---|---|---|---|
~~~
About this tool
HTTP status codes tell clients whether a request worked, failed, or needs a redirect. The number matters: 404 means the resource doesn't exist — don't use it for auth failures (401/403). 500 means your server broke, not the client.
This reference covers the standard codes you'll hit building REST APIs and web apps. Frameworks sometimes pick defaults for you, but knowing the difference between 401 and 403, or 301 and 302, saves debugging time.
~~~