HTTP Status Codes Reference
CLIENTSearchable list of all HTTP status codes (1xx–5xx) with name, meaning, and common use cases.
100Informational
Continue
The server has received the request headers.
101Informational
Switching Protocols
The requester has asked the server to switch protocols.
200Success
OK
Standard response for successful HTTP requests.
201Success
Created
The request has been fulfilled, resulting in the creation of a new resource.
202Success
Accepted
The request has been accepted for processing.
204Success
No Content
The server successfully processed the request but returns no content.
206Success
Partial Content
The server is delivering part of the resource due to a range header.
301Redirection
Moved Permanently
This and all future requests should be directed to the given URI.
302Redirection
Found
Tells the client to look at another URL.
304Redirection
Not Modified
Resource has not been modified since last requested.
307Redirection
Temporary Redirect
Temporarily redirected using same method.
308Redirection
Permanent Redirect
Permanently redirected using same method.
400Client Error
Bad Request
The server cannot process the request due to a client error.
401Client Error
Unauthorized
Authentication is required and has failed or not been provided.
403Client Error
Forbidden
The client does not have access rights to the content.
404Client Error
Not Found
The server cannot find the requested resource.
405Client Error
Method Not Allowed
The request method is known but not supported by the target resource.
408Client Error
Request Timeout
The server would like to shut down this unused connection.
409Client Error
Conflict
Request conflicts with the current state of the server.
410Client Error
Gone
Resource is no longer available and will not be available again.
413Client Error
Payload Too Large
Request entity is larger than limits defined by server.
415Client Error
Unsupported Media Type
The media format of the requested data is not supported.
422Client Error
Unprocessable Entity
The request was well-formed but semantic errors prevent processing.
429Client Error
Too Many Requests
The user has sent too many requests in a given amount of time.
500Server Error
Internal Server Error
A generic error message when an unexpected condition was encountered.
501Server Error
Not Implemented
The server does not recognize the request method.
502Server Error
Bad Gateway
The server received an invalid response from the upstream server.
503Server Error
Service Unavailable
The server is currently unavailable (overloaded or down for maintenance).
504Server Error
Gateway Timeout
The server did not receive a timely response from an upstream server.