Explore detailed information by clicking on each HTTP status code card.
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 is agreeing to do so.
Processing
The server has received and is processing the request, but no response is available yet.
Early Hints
The server is sending preliminary information, such as suggested caching headers.
OK
The request has succeeded.
Created
The request has been fulfilled and resulted in a new resource being created.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The returned meta-information is not from the origin server, but from a local or third-party copy.
No Content
The server has successfully processed the request, but there is no content to return.
Reset Content
The server has successfully processed the request, and the client should reset the document view.
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
Multi-Status
The message body contains multiple status codes for different parts of the request.
Already Reported
The members of a DAV binding have already been enumerated in a previous reply to this request.
IM Used
The server has fulfilled a request for the resource, and the response is a result of an integral transformation applied to the resource.
Multiple Choices
There are multiple options for the resource that the client may follow.
Moved Permanently
The resource has been permanently moved to a new location.
Found
The resource resides temporarily under a different URL.
See Other
The response to the request can be found under another URL using the GET method.
Not Modified
The resource has not been modified since the last request, and the client can use the cached version.
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 URL, and the client should use the same method for the next request.
Permanent Redirect
The resource has permanently moved to a new location, and the client should use the new URL in the future.
Bad Request
The server could not understand the request due to invalid syntax.
Unauthorized
The client must authenticate itself to get the requested response.
Payment Required
This code is reserved for future use. It indicates that payment is required.
Forbidden
The server understands the request, but it refuses to authorize it.
Not Found
The server could not find the requested resource.
Method Not Allowed
The request method is known by the server but is not supported by the resource.
Not Acceptable
The server can generate a response that the client cannot process.
Proxy Authentication Required
The client must authenticate itself with the proxy.
Request Timeout
The server timed out waiting for the request.
Conflict
The request could not be processed due to a conflict with the current state of the resource.
Gone
The resource requested is no longer available and will not be available again.
Length Required
The server requires the request to specify the length of the content.
Precondition Failed
One or more conditions in the request header fields were not met.
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 media type of the request data is not supported by the server.
Range Not Satisfiable
The server cannot provide the requested range of data.
Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
I'm a Teapot
The server is a teapot, and it cannot brew coffee (this is an April Fools' joke from 1998).
Misdirected Request
The request was directed at a server that is not able to produce a response.
Unprocessable Entity
The server understands the content type of the request, but the request is semantically erroneous.
Locked
The resource that is being accessed is locked.
Failed Dependency
The request failed due to a dependency failure.
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 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
The resource is unavailable due to legal reasons.
Internal Server Error
The server has encountered a situation it doesn't know how to handle.
Not Implemented
The server does not recognize the request method, or it lacks the ability to fulfill the request.
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
Service Unavailable
The server is not ready to handle the request, typically due to being overloaded or down for maintenance.
Gateway Timeout
The server, while acting as a gateway or proxy, did not get a response in time from the upstream server.
HTTP Version Not Supported
The server does not support the HTTP protocol version that was used in the request.
Variant Also Negotiates
The server has an internal configuration error: 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.