HTTP Status Codes Reference
A complete HTTP status codes list for web developers. Search, filter, and master REST API status codes with official definitions.
Continue
"The server has received the request headers and the client should proceed to send the request body."
Switching Protocols
"The requester has asked the server to switch protocols and the server has agreed to do so."
OK
"Standard response for successful HTTP requests. The payload depends on the request method."
Created
"The request has been fulfilled, resulting in the creation of a new resource."
Accepted
"The request has been accepted for processing, but the processing has not been completed."
No Content
"The server successfully processed the request and is not returning any content."
Moved Permanently
"The request and all future requests should be directed to the given URI."
Found
"Temporary redirect to a different URI. Used for temporary URL changes."
Not Modified
"Indicates that the resource has not been modified since the version specified by headers."
Bad Request
"The server cannot or will not process the request due to an apparent client error."
Unauthorized
"Authentication is required and has failed or has not yet been provided."
Forbidden
"The request was valid, but the server is refusing action due to insufficient permissions."
Not Found
"The requested resource could not be found but may be available in the future."
Method Not Allowed
"A request method is not supported for the requested resource (e.g., POST on a GET-only route)."
Request Timeout
"The server timed out waiting for the request from the client."
Conflict
"Indicates that the request could not be processed because of conflict in the current state."
I'm a teapot
"The HTCPCP server is a teapot; use this for comedic effect or non-standard errors."
Too Many Requests
"The user has sent too many requests in a given amount of time (rate limiting)."
Internal Server Error
"A generic error message, given when an unexpected condition was encountered."
Bad Gateway
"The server received an invalid response from an upstream server."
Service Unavailable
"The server is currently down for maintenance or is overloaded."
Gateway Timeout
"The server did not receive a timely response from the upstream server."
- 1Use the search bar to look up a specific code (e.g., 403) or a keyword (e.g., 'Not Found').
- 2Filter by category (1xx-5xx) to explore specific types of responses, like errors or redirects.
- 3Click on any card to read a detailed definition of the response code and why it is used.
- 4Check the 'Series' label to understand the general domain of the code (e.g., Client Error, Success).
- 5Use these definitions to correctly implement response handling in your web application.
- Instant Search: Blazing fast lookup for over 50 standard and non-standard HTTP codes.
- Categorized View: Organized grouping by series (e.g., 4xx Client Errors, 5xx Server Errors).
- RFC Aligned: Descriptions strictly follow official protocol standards for high accuracy.
- Visual Indicators: Color-coded cards and icons for instant status recognition.
- Pro Reference: Includes rare codes like 418 I'm a Teapot and 429 Too Many Requests.