HTTP status lookup
Look up any HTTP status code to see its name, description, and whether it is cacheable or retryable. Browse all codes by category or search by number or keyword.
Continue
The server has received the request headers and the client should proceed.
Switching Protocols
The server is switching protocols as requested (e.g. to WebSocket).
Processing
The server has received the request but has not yet completed it (WebDAV).
OK
The request succeeded. The response body contains the requested data.
Created
The request succeeded and a new resource was created. The response includes the Location of the new resource.
Accepted
The request was accepted for processing but has not been completed yet.
No Content
The request succeeded but the response body is intentionally empty (common for DELETE).
Partial Content
The server is delivering only part of the resource due to a Range request header.
Moved Permanently
The resource has been permanently moved. Update your bookmarks and links.
Found
The resource is temporarily at a different URI. Do not update links.
Not Modified
The cached version is still valid - the client can use its cached copy.
Temporary Redirect
Redirect to a different URI with the same HTTP method.
Permanent Redirect
Permanent redirect that preserves the HTTP method.
Bad Request
The server cannot process the request due to a client error (malformed syntax, invalid params).
Unauthorized
Authentication is required. The client must provide valid credentials.
Forbidden
The server understood the request but refuses to authorise it.
Not Found
The server cannot find the requested resource.
Method Not Allowed
The HTTP method is not supported for this endpoint.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the resource (e.g. edit conflict).
Gone
The resource has been permanently removed and will not be available again.
Content Too Large
The request body is larger than the server is willing to process.
Unsupported Media Type
The Content-Type is not supported by this endpoint.
Unprocessable Content
The request was well-formed but contains semantic errors (common in REST APIs).
Too Many Requests
The client has sent too many requests in a given time. Check the Retry-After header.
Internal Server Error
The server encountered an unexpected condition that prevented it from fulfilling the request.
Not Implemented
The server does not support the functionality required to fulfil the request.
Bad Gateway
The server acting as a gateway received an invalid response from an upstream server.
Service Unavailable
The server is temporarily unable to handle requests (overloaded or down for maintenance).
Gateway Timeout
The server acting as a gateway did not get a response in time from an upstream server.