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 via the Upgrade header.

OK

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

Created

The request has been fulfilled and a new resource has been created. Common for POST requests.

Accepted

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

No Content

The server successfully processed the request but is not returning any content.

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. Search engines will update their index.

Found

The resource is temporarily located at a different URL. The client should continue to use the original URL.

Not Modified

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

Temporary Redirect

The request should be repeated with another URI, but future requests should still use the original URI.

Permanent Redirect

The request and all future requests should be directed to the given URI. Like 301 but preserves method.

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 include valid credentials (e.g., JWT, API key, session token).

Forbidden

The server understood the request but refuses to authorize it. Authentication won't help.

Not Found

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

Method Not Allowed

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

Request Timeout

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

Conflict

The request conflicts with the current state of the server. Common with concurrent PUT requests.

Gone

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

Payload Too Large

The request entity is larger than the server is willing to process. Check file size limits.

Unsupported Media Type

The server does not support the media type of the request body. Check the Content-Type header.

Unprocessable Entity

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

Too Many Requests

The user has sent too many requests in a given time period (rate limiting). Retry after the specified delay.

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 the upstream server while acting as a gateway or proxy.

Service Unavailable

The server is currently unavailable (overloaded or down for maintenance). Usually temporary.

Gateway Timeout

The server did not receive a timely response from the upstream server. Common with reverse proxies.