HTTP Status Code Reference
Searchable dictionary of standard HTTP response status codes.
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
Standard response for successful HTTP requests.
Created
The request has been fulfilled, resulting in the creation of a new resource.
Accepted
The request has been accepted for processing, but the processing has not been completed.
No Content
The server successfully processed the request and is not returning any content.
Moved Permanently
This and all future requests should be directed to the given URI.
Found
Tells the client to look at (browse to) another URL.
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
Temporary Redirect
The request should be repeated with another URI; however, future requests should still use the original URI.
Permanent Redirect
The request and all future requests should be repeated using another URI.
Bad Request
The server cannot or will not process the request due to an apparent client error.
Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
Forbidden
The request was valid, but the server is refusing action. The user might not have the necessary permissions.
Not Found
The requested resource could not be found but may be available in the future.
Method Not Allowed
A request method is not supported for the requested resource.
Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource.
I'm a teapot
The server refuses the attempt to brew coffee with a teapot.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance).
Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.