HTTP Status Codes

Continue

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

Switching Protocols

The server is switching protocols as requested by the client — used for WebSocket upgrades.

Processing

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

Early Hints

Used to return hints before the final HTTP message, allowing clients to start preloading resources.

OK

The request succeeded. The meaning of success depends on the HTTP method used.

Created

The request succeeded and a new resource was created. Typically used with POST or PUT.

Accepted

The request has been received but not yet acted upon — used for asynchronous processing.

Non-Authoritative Information

Returned metadata is from a local or third-party copy, not the origin server.

No Content

The request succeeded but there is no content to send in the response body.

Reset Content

Tells the client to reset the document view that caused the request.

Partial Content

The server is delivering only part of the resource due to a Range request header.

Multi-Status

Used in WebDAV; the body contains XML with statuses for multiple independent operations.

Already Reported

Used in WebDAV to avoid enumerating the members of multiple bindings to the same collection.

IM Used

The server has fulfilled a GET request and the response is a representation of the result of instance manipulations.

Multiple Choices

The request has more than one possible response. The user or client should choose one.

Moved Permanently

The resource has been permanently moved to a new URL. Future requests should use the new URL.

Found

The resource is temporarily located at a different URL. The original URL should be used for future requests.

See Other

Directs the client to get the requested resource at a different URI using GET.

Not Modified

The resource has not changed since the last request; the client can use the cached version.

Temporary Redirect

The resource is at a different URI temporarily. The client should use the same method for the new URI.

Permanent Redirect

The resource has been permanently moved. The client must use the new URI and the same HTTP method.

Bad Request

The server cannot process the request due to client error, such as malformed syntax or invalid parameters.

Unauthorized

Authentication is required and has failed or has not been provided.

Payment Required

Reserved for future use. Some APIs use it to indicate the client must pay to access a resource.

Forbidden

The client does not have permission to access the resource, regardless of authentication.

Not Found

The requested resource could not be found. May also be used to hide existence of a forbidden resource.

Method Not Allowed

The HTTP method used is not supported for the requested resource.

Not Acceptable

The requested resource can only return content not acceptable according to the Accept headers.

Proxy Authentication Required

Authentication with a proxy server is required before the request can be fulfilled.

Request Timeout

The server timed out waiting for the request. The client may repeat the request.

Conflict

The request conflicts with the current state of the server, such as a version conflict.

Gone

The resource is no longer available and will not be available again. More permanent than 404.

Length Required

The server requires the Content-Length header field but it is not defined in the request.

Precondition Failed

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

Content Too Large

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

URI Too Long

The URI provided was too long for the server to process.

Unsupported Media Type

The media format of the requested data is not supported by the server.

Range Not Satisfiable

The range specified by the Range header cannot be fulfilled; the resource is smaller than the specified range.

Expectation Failed

The server cannot meet the requirements of the Expect request-header field.

I'm a Teapot

The server refuses to brew coffee because it is a teapot. An April Fools' joke from RFC 2324.

Misdirected Request

The request was directed at a server that is not able to produce a response.

Unprocessable Content

The request was well-formed but was unable to be followed due to semantic errors.

Locked

The resource being accessed is locked (WebDAV).

Failed Dependency

The method could not be performed because of a previous failure (WebDAV).

Too Early

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

Upgrade Required

The client should switch to a different protocol such as TLS/1.3.

Precondition Required

The origin server requires the request to be conditional to prevent lost update problems.

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 received an invalid response from an upstream server while acting as a gateway.

Service Unavailable

The server is not ready to handle the request, typically due to maintenance or overload.

Gateway Timeout

The server acting as a gateway did not receive a timely response from an upstream server.

HTTP Version Not Supported

The HTTP version used in the request is not supported by the server.

Variant Also Negotiates

The server has an internal configuration error: the chosen variant resource is itself configured to engage in content negotiation.

Insufficient Storage

The method could not be performed because the server is unable to store the representation (WebDAV).

Loop Detected

The server detected an infinite loop while processing the request (WebDAV).

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.