Complete HTTP Status Codes Reference
Complete reference of all HTTP status codes organized by class: 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error.
The HTTP status codes most used in practice, grouped by class (informational, success, redirection, client error and server error) with the registered name and a one-line meaning, from 100 Continue and 200 OK to 418 and 511.
Use it when
- You need the exact name and meaning of a status code.
- You are choosing a response code for an API.
Watch out for
- Some names changed over time (for example 413 is now Content Too Large and 422 Unprocessable Content); registered names are in the IANA registry.
- Codes such as 418 are defined for humor or for specific protocols and are not meant for production use.
The data
Codes
45 rows
| Code | Name | Class | Description |
|---|---|---|---|
| 200 | OK | Success | Request succeeded |
| 201 | Created | Success | Resource created successfully |
| 204 | No Content | Success | Request succeeded, no content returned |
| 301 | Moved Permanently | Redirection | Resource permanently moved to new URL |
| 304 | Not Modified | Redirection | Cached version is still valid |
| 400 | Bad Request | Client Error | Malformed request syntax |
| 401 | Unauthorized | Client Error | Authentication required |
| 403 | Forbidden | Client Error | Server refuses to authorize |
| 404 | Not Found | Client Error | Resource not found |
| 429 | Too Many Requests | Client Error | Rate limit exceeded |
| 500 | Internal Server Error | Server Error | Unexpected server condition |
| 502 | Bad Gateway | Server Error | Invalid response from upstream |
| 503 | Service Unavailable | Server Error | Server temporarily overloaded |
| 100 | Continue | Informational | Initial part of the request received; the client should continue sending the body |
| 101 | Switching Protocols | Informational | Server agrees to switch protocols, for example to WebSocket |
| 103 | Early Hints | Informational | Preliminary headers, such as preload links, sent before the final response |
| 202 | Accepted | Success | Request accepted for processing but not yet completed |
| 206 | Partial Content | Success | Server is sending only part of the resource in response to a Range request |
| 207 | Multi-Status | Success | WebDAV response carrying separate status codes for several operations |
| 302 | Found | Redirection | Resource temporarily at a different URL |
| 303 | See Other | Redirection | Retrieve the result at another URL with GET, often after a POST |
| 307 | Temporary Redirect | Redirection | Temporary redirect that preserves the request method |
| 308 | Permanent Redirect | Redirection | Permanent redirect that preserves the request method |
| 405 | Method Not Allowed | Client Error | Method not supported for this resource; the Allow header lists valid methods |
| 406 | Not Acceptable | Client Error | No representation matches the Accept headers sent by the client |
| 408 | Request Timeout | Client Error | Server timed out waiting for the request |
| 409 | Conflict | Client Error | Request conflicts with the current state of the resource |
| 410 | Gone | Client Error | Resource was removed permanently and will not return |
| 412 | Precondition Failed | Client Error | A condition in the request headers, such as If-Match, was not met |
| 413 | Content Too Large | Client Error | Request body is larger than the server will accept |
| 414 | URI Too Long | Client Error | The request URI is longer than the server will process |
| 415 | Unsupported Media Type | Client Error | The request's Content-Type is not supported |
| 416 | Range Not Satisfiable | Client Error | The requested byte range cannot be served |
| 418 | I'm a teapot | Client Error | April Fools' joke code from RFC 2324; not for production use |
| 422 | Unprocessable Content | Client Error | Request is well-formed but contains semantic errors, often validation failures |
| 425 | Too Early | Client Error | Server is unwilling to process a request that might be replayed |
| 426 | Upgrade Required | Client Error | Client must switch to another protocol, indicated in the Upgrade header |
| 428 | Precondition Required | Client Error | Server requires the request to be conditional to avoid lost updates |
| 431 | Request Header Fields Too Large | Client Error | Headers are too large for the server to process |
| 451 | Unavailable For Legal Reasons | Client Error | Access denied because of a legal demand |
| 501 | Not Implemented | Server Error | Server does not support the functionality required to fulfill the request |
| 504 | Gateway Timeout | Server Error | A gateway or proxy did not get a timely response from the upstream server |
| 505 | HTTP Version Not Supported | Server Error | The HTTP version used in the request is not supported |
| 507 | Insufficient Storage | Server Error | Server cannot store the representation needed to complete the request |
| 511 | Network Authentication Required | Server Error | Client must authenticate to gain network access, as on a captive portal |
Fields
The shape of this dataset, read from the data itself: every column, its type and a real value. Agents can use this to plan a query without fetching the whole document.
| Section | Field | Type | Example |
|---|---|---|---|
| codes | code | integer | 200 |
| codes | name | string | OK |
| codes | class | string | Success |
| codes | description | string | Request succeeded |
Fetch the same bytes
The static files contain the same reference rows as the API, with no API rate limit. Live metadata, such as view counts, may differ. Use the API for content negotiation; use the static files for a cacheable snapshot.
curl "https://yjtoon.yunusemrevurgun.com/api/dataset/http-status-codes-complete?format=toon"
const res = await fetch( "https://yjtoon.yunusemrevurgun.com/static-data/dataset/http-status-codes-complete.toon" ); const toon = await res.text();
Rate limit: 120 requests per minute per IP, no key and no signup. API reference →