HTTP Status Codes

Continue

The server has received the request headers and the client should proceed to send the request body.

Switching Protocols

The server is switching protocols as requested by the client via the Upgrade header.

Processing

The server has received and is processing the request, but no response is available yet.

Early Hints

Used to return some response headers before the final HTTP message.

OK

The request has succeeded. The meaning of the success 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 the processing has not been completed.

Non-Authoritative Information

The returned meta-information is from a local or third-party copy, not the origin server.

No Content

The server has fulfilled the request but does not need to return an entity-body.

Reset Content

The server has fulfilled the request and the user agent should reset the document view.

Partial Content

The server has fulfilled the partial GET request for the resource.

Multiple Choices

The target resource has more than one representation, each with its own URI.

Moved Permanently

The target resource has been assigned a new permanent URI.

Found

The target resource resides temporarily under a different URI.

See Other

The server is redirecting the user agent to a different resource via GET.

Not Modified

The resource has not been modified since the last request. Use cached version.

Temporary Redirect

The target resource resides temporarily under a different URI. Method and body must not change.

Permanent Redirect

The target resource has been assigned a new permanent URI. Method and body must not change.

Bad Request

The server could not understand the request due to invalid syntax or malformed data.

Unauthorized

The request requires user authentication.

Payment Required

Reserved for future use. Sometimes used for payment-gated content.

Forbidden

The server understood the request but refuses to authorize it.

Not Found

The origin server did not find a current representation for the target resource.

Method Not Allowed

The method received in the request-line is not supported by the target resource.

Not Acceptable

The target resource does not have a representation acceptable per Accept headers.

Request Timeout

The server did not receive a complete request message within the time it was prepared to wait.

Conflict

The request could not be completed due to a conflict with the current state of the target resource.

Gone

The target resource is no longer available and no forwarding address is known.

Length Required

The server refuses to accept the request without a defined Content-Length.

Precondition Failed

One or more conditions given in the request header fields evaluated to false.

Payload Too Large

The request payload is larger than the server is willing or able to process.

URI Too Long

The request-target is longer than the server is willing to interpret.

Unsupported Media Type

The origin server refuses the request because the payload is in an unsupported format.

I'm a Teapot

The server refuses to brew coffee because it is, permanently, a teapot.

Unprocessable Entity

The server understands the content type and syntax but was unable to process the instructions.

Too Early

The server is unwilling to risk processing a request that might be replayed.

Upgrade Required

The server refuses to perform the request using the current protocol.

Precondition Required

The origin server requires the request to be conditional.

Too Many Requests

The user has sent too many requests in a given amount of time (rate limiting).

Request Header Fields Too Large

The server is unwilling to process the request because its header fields are too large.

Unavailable For Legal Reasons

The server is denying access to the resource as a consequence of a legal demand.

Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request.

Not Implemented

The server does not support the functionality required to fulfill the request.

Bad Gateway

The server, while acting as a gateway or proxy, received an invalid response from an upstream server.

Service Unavailable

The server is currently unable to handle the request due to temporary overloading or maintenance.

Gateway Timeout

The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server.

HTTP Version Not Supported

The server does not support the major version of HTTP that was used in the request.

Variant Also Negotiates

Transparent content negotiation for the request results in a circular reference.

Insufficient Storage

The method could not be performed on the resource because the server is unable to store the representation.

Loop Detected

The server detected an infinite loop while processing the request.

Not Extended

Further extensions to the request are required for the server to fulfill it.

Network Authentication Required

The client needs to authenticate to gain network access.