HTTP Status Codes
Look up HTTP status codes with descriptions and usage examples.
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The server is switching protocols as requested by the client.
Processing
The server has received and is processing the request, but no response is available yet.
Early Hints
Used to return some response headers before final HTTP message.
OK
The request has succeeded. The meaning depends on the HTTP method used.
Created
The request has been fulfilled and a new resource has been created.
Accepted
The request has been accepted for processing, but processing is not complete.
Non-Authoritative Information
The returned metadata is from a local or third-party copy.
No Content
The server successfully processed the request but returns no content.
Reset Content
The server successfully processed the request, asks that the requester reset its document view.
Partial Content
The server is delivering only part of the resource due to a range header.
Multi-Status
The message body contains multiple status codes for multiple resources.
Already Reported
The members of a DAV binding have already been enumerated.
IM Used
The server has fulfilled a GET request for the resource with instance-manipulations.
Multiple Choices
Multiple options for the resource from which the client may choose.
Moved Permanently
The resource has been permanently moved to a new URL.
Found
The resource resides temporarily under a different URI.
See Other
The response can be found under a different URI using GET method.
Not Modified
The resource has not been modified since the last request.
Use Proxy
The requested resource must be accessed through the proxy given by the Location field.
Temporary Redirect
The resource resides temporarily under a different URI.
Permanent Redirect
The resource has been permanently moved to a new URI.
Bad Request
The server cannot process the request due to malformed syntax.
Unauthorized
Authentication is required and has failed or not been provided.
Payment Required
Reserved for future use. Originally intended for digital payment systems.
Forbidden
The server understood the request but refuses to authorize it.
Not Found
The requested resource could not be found on the server.
Method Not Allowed
The request method is not supported for the requested resource.
Not Acceptable
The requested resource cannot generate content acceptable according to Accept headers.
Proxy Authentication Required
The client must first authenticate itself with the proxy.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the server.
Gone
The resource requested is no longer available and will not be available again.
Length Required
The request did not specify the length of its content.
Precondition Failed
The server does not meet one of the preconditions in the request.
Payload Too Large
The request is larger than the server is willing or able to process.
URI Too Long
The URI provided was too long for the server to process.
Unsupported Media Type
The request entity has a media type which the server does not support.
Range Not Satisfiable
The client has asked for a portion of the file that the server cannot supply.
Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
I'm a teapot
The server refuses to brew coffee because it is a teapot. (RFC 2324)
Misdirected Request
The request was directed at a server that is not able to produce a response.
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Locked
The resource that is being accessed is locked.
Failed Dependency
The request failed due to failure of a previous request.
Too Early
The server is unwilling to risk processing a request that might be replayed.
Upgrade Required
The client should switch to a different protocol.
Precondition Required
The origin server requires the request to be conditional.
Too Many Requests
The user has sent too many requests in a given amount of time.
Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large.
Unavailable For Legal Reasons
A server operator has received a legal demand to deny access to a resource.
Internal Server Error
A generic error message when the server encounters an unexpected condition.
Not Implemented
The server does not recognize the request method or lacks ability to fulfill it.
Bad Gateway
The server was acting as a gateway and received an invalid response from upstream.
Service Unavailable
The server is currently unavailable (overloaded or down for maintenance).
Gateway Timeout
The server was acting as a gateway and did not receive a timely response.
HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
Variant Also Negotiates
Transparent content negotiation for the request results in a circular reference.
Insufficient Storage
The server is unable to store the representation needed to complete the request.
Loop Detected
The server detected an infinite loop while processing the request.
Not Extended
Further extensions to the request are required for the server to fulfill it.
Network Authentication Required
The client needs to authenticate to gain network access.
How to use
- Browse status codes by category or search by code/description
- Click on a status code to view detailed information
- Read the description and common usage scenarios
- View example responses for each status code
- Copy the code for quick reference
What are HTTP Status Codes?
HTTP status codes are three-digit numbers returned by servers to indicate the result of a request. They are grouped into five categories: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).