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. The meaning depends on the HTTP method used.
Created
The request has been fulfilled and a new resource has been created.
Accepted
The request has been accepted for processing, but processing has not been completed.
No Content
The server successfully processed the request but is not returning any content.
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
Moved Permanently
The resource has been moved to a new URL permanently.
Found
The resource resides temporarily under a different URL.
Not Modified
The resource has not been modified since the version specified by the request headers.
Temporary Redirect
The request should be repeated with another URI but 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 process the request due to a client error (malformed request syntax, invalid request message framing, or deceptive request routing).
Unauthorized
Authentication is required and has failed or has not been provided.
Forbidden
The server understood the request but refuses to authorize it.
Not Found
The requested resource could not be found on the server.
Method Not Allowed
The method specified in the request is not allowed for the resource.
Request Timeout
The server timed out waiting for the request.
Conflict
The request could not be completed due to a conflict with the current state of the resource.
Gone
The resource is no longer available and will not be available again.
Payload Too Large
The request is larger than the server is willing or able to process.
Unprocessable Entity
The request was well-formed but semantic errors prevent the server from processing it.
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 when the server encounters an unexpected condition.
Not Implemented
The server does not recognize the request method or lacks the ability to fulfill it.
Bad Gateway
The server received an invalid response from an upstream server.
Service Unavailable
The server is currently unavailable (overloaded or down for maintenance).
Gateway Timeout
The server did not receive a timely response from an upstream server.