Complete reference for all HTTP status codes with descriptions and common use cases
Continue
The initial part of a request has been received and has not yet been rejected by the server.
Switching Protocols
The server understands and is willing to comply with the client request for a change of the application protocol.
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 the final HTTP message.
OK
The request succeeded. The meaning of "success" depends on the HTTP method.
Created
The request succeeded, and a new resource was created as a result.
Accepted
The request has been received but not yet acted upon.
Non-Authoritative Information
The returned metadata is not exactly the same as that available from the origin server.
No Content
There is no content to send for this request, but the headers may be useful.
Reset Content
Tells the user agent to reset the document which sent this request.
Partial Content
The server is delivering only part of the data due to a range header sent by the client.
Multi-Status
Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
Already Reported
Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings.
IM Used
The server has fulfilled a GET request for the resource, and the response is a representation of the result.
Multiple Choices
The request has more than one possible response.
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
Found
The URL of the requested resource has been changed temporarily. The new URL is given in the response.
See Other
The server sent this response to direct the client to get the requested resource at another URI.
Not Modified
This is used for caching purposes. It tells the client that the response has not been modified.
Use Proxy
Deprecated. Indicates that a requested response must be accessed by a proxy.
Switch Proxy
Deprecated. No longer used.
Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI.
Permanent Redirect
The requested resource has been definitively moved to the URL given by the Location headers.
Bad Request
The server could not understand the request due to invalid syntax.
Unauthorized
Access to the resource requires authentication.
Payment Required
This response code is reserved for future use. The original aim was to use this code for digital payment systems.
Forbidden
The client does not have access rights to the content.
Not Found
The server can not find the requested resource.
Method Not Allowed
The request method is known by the server but has been disabled and cannot be used.
Not Acceptable
The server cannot find any content that conforms to the criteria given by the client.
Proxy Authentication Required
This response code is similar to 401 except that the authorization is needed by a proxy.
Request Timeout
The server timed out waiting for the request.
Conflict
This response is sent when a request conflicts with the current state of the server.
Gone
This response is sent when the requested content has been permanently deleted from server.
Length Required
The server rejected the request because the Content-Length header field is not defined.
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
Payload Too Large
Request entity is larger than limits defined by server.
URI Too Long
The URL requested by the client is longer than the server is willing to interpret.
Unsupported Media Type
The media format of the requested data is not supported by the server.
Range Not Satisfiable
The range specified by the Range header field in the request cannot be satisfied.
Expectation Failed
The expectation given in the Expect request header field could not be met by the server.
I'm a teapot
The server refuses the attempt to brew coffee with a teapot.
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
Indicates that the server is unwilling to risk processing a request that might be replayed.
Upgrade Required
The server refuses to perform the request using the current 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 ("rate limiting").
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 user-agent requested a resource that cannot legally be provided.
Internal Server Error
The server has encountered a situation it does not know how to handle.
Not Implemented
The request method is not supported by the server and cannot be handled.
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response.
Service Unavailable
The server is not ready to handle the request. Common causes are a server that is down for maintenance.
Gateway Timeout
The server is acting as a gateway and cannot get a response in time.
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
Variant Also Negotiates
The server has an internal configuration error.
Insufficient Storage
The method could not be performed on the resource because the server is unable to store the representation.
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.