Text
HTTP Status Codes
Quick reference for all HTTP status codes with descriptions.
1xx Informational
Continue
Server received request headers, client should send body
Switching Protocols
Server switching protocols as requested
Processing
Server has received and is processing the request
2xx Success
OK
Request succeeded
Created
Resource created successfully
Accepted
Request accepted for processing
No Content
Request succeeded with no response body
Partial Content
Partial resource delivered as requested
3xx Redirection
Multiple Choices
Resource has multiple representations
Moved Permanently
Resource permanently moved to new URL
Found
Resource temporarily at different URL
Not Modified
Resource not modified since last request
Temporary Redirect
Temporary redirect preserving method
Permanent Redirect
Permanent redirect preserving method
4xx Client Error
Bad Request
Server cannot understand the request
Unauthorized
Authentication required
Forbidden
Access denied to resource
Not Found
Resource not found on server
Method Not Allowed
HTTP method not supported
Request Timeout
Server timed out waiting for request
Conflict
Request conflicts with current state
Gone
Resource no longer available
Payload Too Large
Request body exceeds size limit
Too Many Requests
Rate limit exceeded
5xx Server Error
Internal Server Error
Unexpected server error
Not Implemented
Server does not support functionality
Bad Gateway
Invalid response from upstream server
Service Unavailable
Server temporarily unavailable
Gateway Timeout
Upstream server timeout
How it works
HTTP status codes are three-digit numbers that servers return to indicate the outcome of a request. Understanding these codes is essential for debugging APIs, troubleshooting web applications, and building robust HTTP clients. This reference organizes all standard status codes into their official categories, making it easy to find the information you need during development or incident response.
The five categories cover every possible response scenario. 1xx codes indicate informational responses, rarely seen in typical web development. 2xx codes signal success, with 200 OK being the most common. 3xx codes handle redirection, crucial for SEO and URL management. 4xx codes indicate client errors like 404 Not Found or 403 Forbidden. 5xx codes signal server errors, which often require immediate attention from operations teams.
Each entry includes the numeric code, its official name, and a practical description of when you will encounter it. The color coding provides instant visual recognition: green for success, yellow for redirection, and red for errors. This matches the mental model most developers have built from years of seeing these codes in logs and browser dev tools. The search feature lets you quickly find codes by number or name.
Keep this reference handy when debugging API responses, writing error handling code, or documenting your own API's response behavior. Understanding status codes helps you build better error messages, implement proper retry logic, and communicate clearly with API consumers. The standardized meanings ensure that developers across teams and organizations share a common vocabulary for discussing HTTP interactions.