Search HTTP status codes and understand what each response means. Filter by category, code, or phrase and quickly find common client and server errors.
The server received the initial request headers and the client should continue sending the body.
The server is switching protocols as requested by the client.
The request succeeded and the response contains the requested resource.
The request succeeded and a new resource was created.
The server accepted the request for processing, but it is not finished yet.
The request succeeded and there is no response body.
The server is returning only the requested part of a resource.
The resource has a new permanent URL.
The resource is temporarily available at a different URL.
The client should fetch the resource using GET at another URL.
The cached version can be used because the resource has not changed.
The resource is temporarily at another URL and the same method should be used.
The resource has moved permanently and the same method should be reused.
The server could not understand the request due to invalid syntax or missing data.
Authentication is required and has failed or was not provided.
The client is authenticated but does not have permission to access the resource.
The requested resource could not be found.
The request method is not supported for this resource.
The server timed out waiting for the client to finish the request.
The request conflicts with the current state of the resource.
The resource no longer exists and will not be available again.
The request body is larger than the server is willing to process.
The request body format is not supported by the server.
An April Fools' status code used when a server refuses to brew coffee in a teapot.
The request is well-formed but contains semantic validation errors.
The client has sent too many requests in a given period.
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
A gateway or proxy received an invalid response from an upstream server.
The server is temporarily unavailable, often due to overload or maintenance.
A gateway or proxy timed out waiting for an upstream server.