HTTP Status Codes
Browse and search all HTTP status codes with descriptions.
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
OK
The request has succeeded.
Created
The request has succeeded and a new resource has been created as a result.
Accepted
The request has been received but not yet acted upon.
No Content
There is no content to send for this request, but the headers may be useful.
Moved Permanently
The URL of the requested resource has been changed permanently.
Found
The URI of requested resource has been changed temporarily.
Not Modified
The client can use the cached version of the requested resource.
Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI with the same method.
Permanent Redirect
The resource is now permanently located at another URI, specified by the Location response header.
Bad Request
The server cannot or will not process the request due to a client error.
Unauthorized
The client must authenticate itself to get the requested response.
Forbidden
The client does not have access rights to the content.
Not Found
The server cannot find the requested resource.
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
Request Timeout
The server would like to shut down this unused connection.
Conflict
The request conflicts with the current state of the server.
Gone
The requested content has been permanently deleted from the server.
Content Too Large
The request entity is larger than limits defined by server.
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
Unsupported Media Type
The media format of the requested data is not supported by the server.
Unprocessable Content
The request was well-formed but could not be followed due to semantic errors.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Internal Server Error
The server has encountered a situation it does not know how to handle.
Not Implemented
The request method is not supported by the server and cannot be handled.
Bad Gateway
The server, while working as a gateway, got an invalid response.
Service Unavailable
The server is not ready to handle the request.
Gateway Timeout
The server is acting as a gateway and cannot get a response in time.