HTTP Status Codes

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

The server agrees to switch protocols as requested by the client.

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

The request succeeded and a new resource was created as a result.

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

The server successfully processed the request and returns no content.

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

The resource has permanently moved to a new URL.

The resource has temporarily moved to a different URL.

The client can use its cached version; the resource hasn't changed.

Temporary redirect; the request method must not change.

Permanent redirect; the request method must not change.

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

Authentication is required. The client must authenticate to get the resource.

The client is authenticated but doesn't have permission to access the resource.

The server cannot find the requested resource.

The HTTP method is not supported for this endpoint.

The server timed out waiting for the client to complete the request.

The request conflicts with the current state of the resource.

The resource is permanently gone and no forwarding address is available.

The request body exceeds the server's size limit.

The server refuses the request because the media type is not supported.

The request is well-formed but has semantic errors.

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

The server encountered an unexpected error and cannot complete the request.

The server doesn't support the functionality required to fulfill the request.

The server, acting as a gateway, received an invalid response from an upstream server.

The server is temporarily unavailable, usually due to maintenance or overload.

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

The server cannot store the representation needed to complete the request.

The server detected an infinite loop while processing the request.