Reference
Search HTTP status codes with meanings and categories.
Runs entirely in your browser
Nothing you paste is uploaded. Monaco and Prettier load on demand from this origin.
Search
| Code | Name | Meaning |
|---|---|---|
| 100 | Continue | Interim response; keep sending the request body. |
| 101 | Switching Protocols | Server agrees to switch protocols. |
| 200 | OK | Standard success response. |
| 201 | Created | Resource created; often returns Location. |
| 202 | Accepted | Accepted for processing, not yet complete. |
| 204 | No Content | Success with no response body. |
| 206 | Partial Content | Range request satisfied. |
| 301 | Moved Permanently | Resource permanently moved. |
| 302 | Found | Temporary redirect. |
| 304 | Not Modified | Cached copy is still valid. |
| 307 | Temporary Redirect | Redirect preserving method. |
| 308 | Permanent Redirect | Permanent redirect preserving method. |
| 400 | Bad Request | Malformed request syntax. |
| 401 | Unauthorized | Authentication required or failed. |
| 403 | Forbidden | Authenticated but not allowed. |
| 404 | Not Found | Resource does not exist. |
| 405 | Method Not Allowed | HTTP method not supported here. |
| 409 | Conflict | Request conflicts with current state. |
| 410 | Gone | Resource permanently removed. |
| 418 | I'm a teapot | RFC 2324 easter egg. |
| 422 | Unprocessable Entity | Validation failed. |
| 429 | Too Many Requests | Rate limited; check Retry-After. |
| 500 | Internal Server Error | Generic server failure. |
| 501 | Not Implemented | Server lacks the functionality. |
| 502 | Bad Gateway | Invalid upstream response. |
| 503 | Service Unavailable | Overloaded or down for maintenance. |
| 504 | Gateway Timeout | Upstream did not respond in time. |
There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check. See how it stays private.
How to HTTP status codes
- Search a code. Type a number like 404 or a keyword.
- Read the meaning. See what the code signals and its category.
- Apply it. Use the right code in your API responses.
Choosing the right status code makes an API predictable — clients and caches behave based on it. This reference clears up the common confusions (401 vs 403, 301 vs 302, 200 vs 204) so responses say what you mean.
For the headers that accompany those responses, see the HTTP header reference; to test real responses, use the HTTP client.
Frequently asked questions
What's the difference between 401 and 403?
401 Unauthorized means you're not authenticated (log in); 403 Forbidden means you're authenticated but not allowed. The distinction matters for correct API behavior.
When should I use 301 vs 302?
301 is a permanent redirect (search engines update their index); 302 is temporary. Use 301 for moved pages and 302 for short-lived redirects.
Is anything fetched?
No. The reference is built in, so it works offline and contacts no server.