Free HTTP status code reference. Browse all standard HTTP response codes organized by category — 1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error and 5xx Server Error. Search by code number or description with detailed explanations and usage examples for REST API development.
The server has received the request headers and the client should proceed to send the request body.
The server is switching protocols as requested by the client via the Upgrade header.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before final HTTP message. Allows preloading resources.
The request succeeded. The meaning depends on the HTTP method used.
The request succeeded and a new resource was created as a result.
The request has been received but not yet acted upon. It is intended for asynchronous processing.
The returned metadata is from a local or third-party copy, not the origin server.
The server successfully processed the request and is not returning any content.
The server successfully processed the request and asks the client to reset the document view.
The server is delivering only part of the resource due to a range header sent by the client.
A WebDAV response that conveys information about multiple resources.
Used in WebDAV to indicate that members have already been enumerated.
The request has more than one possible response. The user should choose one of them.
The resource has been permanently moved to a new URL. Search engines will update their links.
The resource is temporarily located at a different URL. The client should continue to use the original URL.
The response can be found at another URL using a GET request.
The resource has not been modified since the last request. Used for caching.
The resource is temporarily at a different URL. The method and body should not change.
The resource has permanently moved. The method and body should not change.
The server cannot process the request due to malformed syntax or invalid parameters.
Authentication is required. The client must provide valid credentials.
Reserved for future use. Some APIs use this for rate limiting or paid features.
The server understood the request but refuses to authorize it. Authentication won't help.
The server cannot find the requested resource. The URL may be invalid or the resource deleted.
The request method is not supported for the requested resource.
The server cannot produce a response matching the Accept headers sent by the client.
The client must authenticate with a proxy before the request can proceed.
The server timed out waiting for the client to send the request.
The request conflicts with the current state of the resource (e.g., edit conflicts).
The resource has been permanently deleted and will not be available again.
The server requires a Content-Length header in the request.
One or more conditions in the request header fields evaluated to false.
The request body is larger than the server is willing to process.
The URI is too long for the server to process.
The media format of the requested data is not supported by the server.
The range specified in the Range header cannot be fulfilled.
The server refuses to brew coffee because it is a teapot. An April Fools' joke from RFC 2324.
The request was well-formed but contains semantic errors (WebDAV / validation errors).
The server is unwilling to process a request that might be replayed.
The client has sent too many requests in a given time period (rate limiting).
The server refuses the request because header fields are too large.
The resource is unavailable due to legal demands (censorship, DMCA).
The server encountered an unexpected error that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
The server acting as a gateway received an invalid response from the upstream server.
The server is temporarily unable to handle the request (overloaded or under maintenance).
The server acting as a gateway did not receive a timely response from the upstream server.
The server does not support the HTTP version used in the request.
The server cannot store the representation needed to complete the request (WebDAV).
The server detected an infinite loop while processing the request (WebDAV).
The client needs to authenticate to gain network access (captive portals).
52 results