HTTP Status Codes Directory & Guide

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

Requester has asked the server to switch protocols and server agreed.

Standard response for successful HTTP requests.

Request fulfilled, resulting in the creation of a new resource.

Request accepted for processing, but processing has not completed.

Server successfully fulfilled request and there is no additional content to send.

Resource has been assigned a new permanent URI.

Resource resides temporarily under a different URI.

Resource has not been modified since the version specified by request headers.

Target resource resides temporarily under a different URI; client must not change method.

Target resource has been assigned a new permanent URI; client must not change method.

Server cannot or will not process the request due to client error (e.g. malformed syntax).

Request has not been applied because it lacks valid authentication credentials.

Server understood request but refuses to authorize it.

Server cannot find the requested resource.

Request method is recognized by server but not supported by target resource.

Request could not be processed because of conflict in request (e.g. duplicate email).

Server understands content type and syntax, but cannot process contained instructions.

User has sent too many requests in a given amount of time (rate limiting).

Server encountered an unexpected condition that prevented it from fulfilling request.

Server, while acting as a gateway or proxy, received invalid response from inbound server.

Server is not ready to handle request (overloaded or down for maintenance).

Server, while acting as gateway, did not receive timely response from upstream server.