HTTP Status Code Reference
New🔥 PopularQuick lookup: what every HTTP status code means (200, 404, 500…)
- 1Paste code, JSON, or data
- 2Choose format, minify, or validate
- 3Copy the clean output
The server has received the request headers; the client may proceed with the request body.
The server is switching protocols as requested (e.g. WebSocket upgrade).
The request succeeded. Standard success response.
The request succeeded and a new resource was created.
Success with no response body (common for DELETE).
The resource has permanently moved to a new URL.
Temporary redirect. The resource is temporarily at another URL.
Cached version is still valid; no need to re-download.
Temporary redirect that preserves the HTTP method.
Permanent redirect that preserves the HTTP method.
The server cannot process the request due to client error (malformed syntax).
Authentication is required and has failed or not been provided.
The server understood the request but refuses to authorize it.
The requested resource could not be found on the server.
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 and will not be available again.
The request body is larger than the server is willing to process.
The media format of the request is not supported.
Well-formed request but semantic errors (common in APIs).
The user has sent too many requests in a given time (rate limiting).
A generic server error occurred.
The server does not support the functionality required.
The server received an invalid response from an upstream server.
The server is temporarily unavailable (overload or maintenance).
The upstream server did not respond in time.
Reference
The server has received the request headers; the client may proceed with the request body.
27 codes shown
Part of these collections
Parsed and converted in your browser — nothing is logged.
Popular searches