HTTP Status Codes
Search and browse HTTP status codes with their meaning and when each one is used.
The client should continue with its request.
The server is switching protocols as requested.
The server has received and is processing the request.
Used to return some response headers before the final response.
The request succeeded.
The request succeeded and a new resource was created.
The request was accepted but not yet acted upon.
Returned metadata is from a copy, not the origin.
The request succeeded; there is no content to return.
Tells the client to reset the document that sent the request.
The server is delivering part of the resource (range request).
The request has more than one possible response.
The resource has permanently moved to a new URL.
The resource is temporarily at a different URL.
The response can be found at another URL using GET.
The cached version of the resource is still valid.
Temporary redirect that preserves the request method.
Permanent redirect that preserves the request method.
The server cannot process the request due to a client error.
Authentication is required and has failed or not been provided.
Reserved for future use; sometimes used for paid APIs.
The client is authenticated but not allowed to access this.
The server cannot find the requested resource.
The request method is not supported for this resource.
No content matching the request's Accept headers is available.
The server timed out waiting for the request.
The request conflicts with the current state of the resource.
The resource is permanently gone and will not return.
The request must specify a Content-Length header.
A precondition in the request headers was not met.
The request body is larger than the server will accept.
The requested URI is longer than the server will accept.
The request body format is not supported.
An April Fools' joke from RFC 2324; the server refuses to brew coffee.
The request was well-formed but is semantically invalid.
The server is unwilling to process a request that may be replayed.
The client should switch to a different protocol.
The origin server requires the request to be conditional.
The client has sent too many requests in a given time.
Header fields are too large for the server to process.
The resource is unavailable for legal reasons.
The server encountered an unexpected condition.
The server does not support the functionality required.
An upstream server returned an invalid response.
The server is not ready, often overloaded or down for maintenance.
An upstream server did not respond in time.
The HTTP version used in the request is not supported.
The server cannot store the representation needed to complete the request.
The client needs to authenticate to gain network access.
A quick reference of common HTTP status codes grouped by class (1xx–5xx). Everything is bundled with the page — no requests are made.