HTTP Status Code Reference

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

The server is switching protocols as requested by the client (e.g. HTTP → WebSocket).

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

Used to return some response headers before the final HTTP message, for link preloading.

Standard successful response for GET, POST, PUT, PATCH, DELETE requests.

A new resource was successfully created. Typically returned after POST or PUT.

The request has been accepted for processing, but processing is not complete.

Success, but no response body. Common for DELETE requests.

The server is delivering only part of the resource (range requests, video streaming).

The resource has been permanently moved. Browsers and search engines update their links.

Temporary redirect. The client should continue to use the original URL for future requests.

Redirect after a POST — tells client to GET a different URL.

Cached content is still valid. Server tells client to use its cached version.

Temporary redirect, but the method and body must not change (unlike 302).

Permanent redirect, method and body must not change (unlike 301).

The server cannot process the request due to malformed syntax or invalid input.

Authentication is required. The client must authenticate to get the requested response.

The server understood the request but refuses to authorize it. Different from 401.

The server cannot find the requested resource. The URL is not recognized.

The request method is not allowed for this resource (e.g. PUT on a read-only endpoint).

The server timed out waiting for the request.

The request conflicts with the current state of the resource (e.g. duplicate entry).

The resource is permanently deleted and will not be available again.

The request entity is larger than limits defined by the server.

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

The request was well-formed but unable to be processed due to semantic errors. Common in REST APIs.

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

A generic server error. Something went wrong on the server side.

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

The server received an invalid response from an upstream server.

The server is not ready to handle the request (overloaded or down for maintenance).

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

The server is unable to store the representation needed to complete the request.