The request succeeded.
The request succeeded and created a resource.
The request was accepted for processing, which may not have finished.
The request succeeded and there is no body to return.
Only part of the resource was returned, as a range request asked for.
The resource has permanently moved.
The resource is temporarily at another URL.
The response lives at another URL and should be fetched with GET.
The cached copy is still valid.
Temporary redirect that keeps the request method.
Permanent redirect that keeps the request method.
The server could not understand the request.
Authentication is required or has failed.
Reserved for payment; some storefronts use it for paywalled content.
The server understood the request but refuses it (often a bot challenge).
The resource does not exist.
The request method is not allowed for this resource.
The server cannot produce a response matching the Accept headers.
The server timed out waiting for the request.
The request conflicts with the current state of the resource.
The resource is gone and will not return.
The request body is larger than the server allows.
The request body's media type is not supported.
The request was well-formed but could not be processed.
Too many requests were sent; the client is being rate limited.
The resource is unavailable for legal reasons.
The server hit an unexpected error.
The server does not support the requested functionality.
A gateway or proxy got an invalid response from upstream.
The server is overloaded or down for maintenance.
A gateway or proxy timed out waiting for upstream.
Common HTTP status codes, named in
UPPER_SNAKE_CASEafter their reason phrases.Example
Source