HTTP Status Codes.
Look up any HTTP status code, its category and meaning.
The client should continue with its request.
The server is switching protocols as requested.
The request succeeded.
The request succeeded and a new resource was created.
The request was accepted for processing but is not complete.
The request succeeded; there is no body to return.
The server delivered part of the resource (range request).
The resource has a new permanent URL.
The resource is temporarily at a different URL.
The cached copy is still valid; no body returned.
Repeat the request at another URL, keeping the method.
The resource moved permanently; keep the method.
The server could not understand the request.
Authentication is required or has failed.
The server understood the request but refuses to authorize it.
The requested resource does not exist.
The HTTP method is not supported for this resource.
The server timed out waiting for the request.
The request conflicts with the current state of the resource.
The resource is permanently gone with no forwarding address.
The request body is larger than the server will accept.
The request body format is not supported.
An April Fools joke from RFC 2324; sometimes used as a decoy.
The request was well-formed but semantically invalid.
The client has sent too many requests in a given time.
Access denied for legal demand.
The server hit an unexpected condition.
The server does not support the functionality required.
An upstream server returned an invalid response.
The server is overloaded or down for maintenance.
An upstream server did not respond in time.
Three simple steps
How to use HTTP Status Codes
Search
Type a code number or a keyword.
Read the meaning
See the name, class and description.
Use it
Pick the right code for your API response.