Look up the meaning of any HTTP status code.
Runs in your browserThere are dozens of HTTP status codes beyond the common ones (200, 404, 500), and remembering the precise meaning of a less common one (409, 422, 451) when debugging an API response usually means a quick search anyway. This tool looks up the meaning of any HTTP status code instantly, saving that search when you're debugging an API response.
The initial part of a request has been received and the client should continue with the rest of it.
The server is switching protocols as requested by the client.
The request succeeded.
The request succeeded and a new resource was created as a result.
The request has been received but not yet acted upon.
The request succeeded but there is no content to send back.
Only part of the resource is being sent, due to a range header sent by the client.
The resource has been permanently moved to a new URL.
The resource resides temporarily under a different URL.
The resource hasn't changed since the last request, the cached version can be used.
The resource has temporarily moved, and future requests should still use the original URL, keeping the same HTTP method.
The resource has permanently moved, and future requests should use the new URL, keeping the same HTTP method.
The server can't process the request due to a client error, such as malformed syntax.
Authentication is required and has failed or not been provided.
Reserved for future use, originally intended for digital payment systems.
The client's identity is known but it doesn't have permission to access the resource.
The server can't find the requested resource.
The request method is known but not supported for this resource.
The server timed out waiting for the request.
The request conflicts with the current state of the resource.
The requested resource is no longer available and won't be available again.
The request body is larger than the server is willing or able to process.
The requested URI is longer than the server is willing to interpret.
The media format of the requested data isn't supported by the server.
An April Fools' joke from RFC 2324, a teapot receiving a request to brew coffee.
The request was well-formed but contains semantic errors.
The client has sent too many requests in a given amount of time (rate limiting).
The server encountered an unexpected condition that prevented it from fulfilling the request.
The request method isn't supported by the server and can't be handled.
The server, acting as a gateway, got an invalid response from an upstream server.
The server isn't ready to handle the request, often due to maintenance or overload.
The server, acting as a gateway, didn't get a response in time from an upstream server.
The HTTP version used in the request isn't supported by the server.