HTTP Status Codes Directory
Quickly identify response codes, understand why errors happen, and find exact solutions for your API and web application development.
1xx1xx Informational
Request received, continuing process.
2xx2xx Success
The action was successfully received, understood, and accepted.
The standard response for successful HTTP requests. The payload returned depends on the request method.
The request has been fulfilled, resulting in the creation of a new resource on the server.
The request has been accepted for processing, but the processing has not been completed.
The server successfully processed the request, but is not returning any content in the response body.
The server is delivering only part of the resource due to a Range header sent by the client.
3xx3xx Redirection
Further action must be taken to complete the request.
The requested resource has been assigned a new permanent URI and any future references should use one of the returned URIs.
The requested resource resides temporarily under a different URI. Future requests should continue using the original URI.
Indicates that the resource has not been modified since the version specified by the conditional request headers (If-Modified-Since or If-None-Match).
The request should be repeated with another URI; however, future requests should still use the original URI without changing the HTTP method.
The request and all future requests should be repeated using another URI, strictly preserving the HTTP method.
4xx4xx Client Error
The request contains bad syntax or cannot be fulfilled.
The server cannot or will not process the request due to an apparent client error (e.g., malformed syntax, invalid framing, or deceptive routing).
The client must authenticate itself to get the requested response. Similar to 403, but specific for missing or invalid credentials.
The server understood the request but refuses to authorize it. Unlike 401, re-authenticating with the same credentials will make no difference.
The server cannot find the requested resource. Links that lead to a 404 are often called broken or dead links.
The request method is recognized by the server but is not supported by the target resource.
The server timed out waiting for the client to send a complete request.
Indicates that the request could not be processed because of conflict in the current state of the resource.
Indicates that the target resource is no longer available at the origin server and that this condition is likely to be permanent.
The request entity is larger than limits defined by server configuration.
The origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.
The request was well-formed but was unable to be followed due to semantic errors.
The user has sent too many requests in a given amount of time (rate limiting).
5xx5xx Server Error
The server failed to fulfill an apparently valid request.
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
The server, while acting as a gateway or proxy, received an invalid response from the inbound server it accessed.
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.
The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.
The server does not support, or refuses to support, the major version of HTTP that was used in the request message.