HTTP Status Code Lookup & Dictionary
Browse, search, and filter HTTP response status code specifications, categories, and common usages.
The server has received the request headers and the client should proceed to send the request body.
The requester has asked the server to switch protocols and the server has agreed to do so.
Standard response for successful HTTP requests. The actual response will depend on the request method used.
The request has been fulfilled, resulting in the creation of a new resource.
The request has been accepted for processing, but the processing has not been completed.
The server successfully processed the request, and is not returning any content.
This and all future requests should be directed to the given URI.
Tells the client to look at another URL temporarily. (Previously 'Moved Temporarily').
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
A request method is not supported for the requested resource (e.g., a GET request on a POST endpoint).
Indicates that the request could not be processed because of conflict in the current state of the resource.
The request was well-formed but was unable to be followed due to semantic errors (e.g. invalid Pydantic body validation).
The user has sent too many requests in a given amount of time ('rate limiting').
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
What are HTTP Status Codes?
HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes:
- 1xx Informational: Request received, continuing process.
- 2xx Success: The action was successfully received, understood, and accepted.
- 3xx Redirection: Further action must be taken in order to complete the request.
- 4xx Client Error: The request contains bad syntax or cannot be fulfilled.
- 5xx Server Error: The server failed to fulfill an apparently valid request.