HTTP Status Code Reference

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 (e.g., upgrading to WebSocket).

OK

The request succeeded. The response body contains the requested data.

Created

The request succeeded and a new resource was created. Typically returned after POST requests.

No Content

The request succeeded but there is no content to return. Common for DELETE requests.

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 permanently moved to a new URL. Browsers and search engines update their records.

Found (Temporary Redirect)

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

Not Modified

The resource has not been modified since the last request. The client can use its cached version.

Temporary Redirect

Like 302 but the HTTP method must not change. A POST request stays a POST after redirect.

Permanent Redirect

Like 301 but the HTTP method must not change. A POST request stays a POST after redirect.

Bad Request

The server cannot process the request due to malformed syntax, invalid parameters, or missing required fields.

Unauthorized

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

Forbidden

The client is authenticated but does not have permission to access the resource.

Not Found

The server cannot find the requested resource. The URL may be wrong or the resource may have been deleted.

Method Not Allowed

The HTTP method used is not allowed for this resource (e.g., sending POST to a GET-only endpoint).

Request Timeout

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

Conflict

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

Gone

The resource has been permanently deleted and will not be available again. Unlike 404, this is intentional.

Unprocessable Entity

The request is well-formed but contains semantic errors. Common in REST APIs for validation failures.

Too Many Requests

The client has sent too many requests in a given time period. Rate limiting is in effect.

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

Service Unavailable

The server is temporarily unable to handle the request due to overload or maintenance.

Gateway Timeout

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