HTTP Status Code Reference
Searchable reference of all HTTP status codes with descriptions and use cases
61 status codes
Continue
The server has received the request headers and the client should proceed.
Switching Protocols
Server is switching to the protocol specified in the Upgrade header.
Processing
Server has received and is processing the request, but no response is yet available.
Early Hints
Used to preload resources while the server prepares a full response.
OK
The request succeeded.
Created
The request succeeded and a new resource was created.
Accepted
Request received but processing has not been completed.
Non-Authoritative Information
The response was transformed by a proxy.
No Content
The request succeeded but there is no content to return.
Reset Content
The request succeeded; client should reset the document view.
Partial Content
The server is delivering only part of the resource.
Multi-Status
Multiple status codes for multiple independent operations.
Already Reported
Members of a DAV binding already enumerated in a previous reply.
IM Used
The server fulfilled a GET request using instance manipulations.
Multiple Choices
Multiple options are available for the requested resource.
Moved Permanently
The resource has permanently moved to a new URL.
Found
The resource is temporarily at a different URL.
See Other
Redirect to another resource using GET, typically after a POST.
Not Modified
The cached version of the resource is still valid.
Temporary Redirect
Temporarily redirect to another URL, preserving the HTTP method.
Permanent Redirect
Permanently redirect to another URL, preserving the HTTP method.
Bad Request
The server cannot process the request due to a client error.
Unauthorized
Authentication is required and has failed or not been provided.
Payment Required
Reserved for future use; sometimes used for API quota limits.
Forbidden
The client is authenticated but not authorized to access the resource.
Not Found
The server cannot find the requested resource.
Method Not Allowed
The HTTP method is not supported for the requested resource.
Not Acceptable
No content matches the client's Accept headers.
Proxy Authentication Required
Authentication with a proxy server is required.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the server.
Gone
The resource existed but has been permanently deleted.
Length Required
A Content-Length header is required.
Precondition Failed
Precondition headers (If-Match, If-Unmodified-Since) evaluated to false.
Content Too Large
The request body exceeds the server's size limit.
URI Too Long
The request URI is longer than the server will interpret.
Unsupported Media Type
The request's Content-Type is not supported by the server.
Range Not Satisfiable
The Range header cannot be fulfilled.
Expectation Failed
The Expect request header cannot be met by the server.
I'm a Teapot
The server refuses to brew coffee because it is a teapot.
Misdirected Request
The request was directed to a server that cannot produce a response.
Unprocessable Content
The request is well-formed but has semantic errors.
Locked
The source or destination resource is locked.
Failed Dependency
The request failed because a previous request it depended on failed.
Too Early
The server is unwilling to process a request that might be replayed.
Upgrade Required
The client must switch to a different protocol.
Precondition Required
The server requires the request to be conditional.
Too Many Requests
The client has sent too many requests in a given time (rate limiting).
Request Header Fields Too Large
The request's headers are too large for the server to process.
Unavailable For Legal Reasons
The resource cannot be provided for legal reasons.
Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
Not Implemented
The server does not support the functionality required to fulfill the request.
Bad Gateway
The server received an invalid response from an upstream server.
Service Unavailable
The server is temporarily unable to handle the request.
Gateway Timeout
The gateway did not receive a timely response from an upstream server.
HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
Variant Also Negotiates
Transparent content negotiation resulted in a circular reference.
Insufficient Storage
The server cannot 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.
Network Authentication Required
The client needs to authenticate to gain network access.