HTTP STATUS CODES

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

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

The request has succeeded. The response body contains the requested resource.

The request has been fulfilled and a new resource has been created. Typically returned after POST requests.

The request has been accepted for processing, but the processing has not been completed yet.

The server successfully processed the request but is not returning any content. Common for DELETE operations.

The server is delivering only part of the resource due to a Range header sent by the client.

The resource has been permanently moved to a new URL. Search engines will update their index.

The resource has been temporarily moved to a different URL. The client should continue using the original URL.

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

The request should be repeated with the same HTTP method at a different URL. Preserves the request method.

The resource has permanently moved. Like 301, but the request method must not change.

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

Authentication is required. The client must include valid credentials (API key, token, or login).

The server understood the request but refuses to authorize it. Authentication will not help.

The requested resource could not be found on the server. Check the URL for typos.

The HTTP method used is not supported for this resource. Check if you should use GET, POST, PUT, etc.

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

The request conflicts with the current state of the server. Common in concurrent update scenarios.

The resource is no longer available and will not be available again. Unlike 404, this is permanent.

The request body exceeds the maximum size the server is willing to process.

The server does not support the Content-Type of the request body.

The request was well-formed but contains semantic errors. Common in validation failures.

Rate limit exceeded. The client has sent too many requests in a given time period. Retry after the specified delay.

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

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

The server received an invalid response from an upstream server. Common with reverse proxies and load balancers.

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

The server did not receive a timely response from an upstream server. Similar to 502 but specifically a timeout.