Share
Look up any HTTP status code with description and use cases.
Searchable reference for all HTTP status codes — 1xx informational, 2xx success, 3xx redirect, 4xx client error, and 5xx server error. Each code includes a description, common use cases, and example scenarios.
Quickly identify and understand any HTTP response code to debug web applications and REST APIs.
Access the HTTP Status Code tool
Navigate to the HTTP Status Code Reference tool page to view the complete list of status categories.
Search for a specific code
Use the search or filter function to find a specific status code like 404, 200, or 500.
Review the code description
Read the detailed explanation for your selected code to understand its meaning and impact on the client or server.
Analyze common use cases
Examine the provided example scenarios to see how the status code is typically implemented in real-world development.
Apply the fix or configuration
Use the insights gained from the reference to update your API responses or troubleshoot server errors.
Estimated time: PT1M
Share this tool
100Continue1xxThe server received the request headers and the client should proceed to send the request body.
101Switching Protocols1xxThe server is switching protocols as requested by the client (e.g. HTTP → WebSocket).
102Processing1xxWebDAV: the server has received and is processing the request, but no response is available yet.
103Early Hints1xxUsed to return some response headers before the final HTTP message, for link preloading.
200OK2xxStandard successful response for GET, POST, PUT, PATCH, DELETE requests.
201Created2xxA new resource was successfully created. Typically returned after POST or PUT.
202Accepted2xxThe request has been accepted for processing, but processing is not complete.
204No Content2xxSuccess, but no response body. Common for DELETE requests.
206Partial Content2xxThe server is delivering only part of the resource (range requests, video streaming).
301Moved Permanently3xxThe resource has been permanently moved. Browsers and search engines update their links.
302Found3xxTemporary redirect. The client should continue to use the original URL for future requests.
303See Other3xxRedirect after a POST — tells client to GET a different URL.
304Not Modified3xxCached content is still valid. Server tells client to use its cached version.
307Temporary Redirect3xxTemporary redirect, but the method and body must not change (unlike 302).
308Permanent Redirect3xxPermanent redirect, method and body must not change (unlike 301).
400Bad Request4xxThe server cannot process the request due to malformed syntax or invalid input.
401Unauthorized4xxAuthentication is required. The client must authenticate to get the requested response.
403Forbidden4xxThe server understood the request but refuses to authorize it. Different from 401.
404Not Found4xxThe server cannot find the requested resource. The URL is not recognized.
405Method Not Allowed4xxThe request method is not allowed for this resource (e.g. PUT on a read-only endpoint).
408Request Timeout4xxThe server timed out waiting for the request.
409Conflict4xxThe request conflicts with the current state of the resource (e.g. duplicate entry).
410Gone4xxThe resource is permanently deleted and will not be available again.
413Content Too Large4xxThe request entity is larger than limits defined by the server.
415Unsupported Media Type4xxThe media format of the requested data is not supported by the server.
422Unprocessable Entity4xxThe request was well-formed but unable to be processed due to semantic errors. Common in REST APIs.
429Too Many Requests4xxThe user has sent too many requests in a given time (rate limiting).
500Internal Server Error5xxA generic server error. Something went wrong on the server side.
501Not Implemented5xxThe server does not support the functionality required to fulfill the request.
502Bad Gateway5xxThe server received an invalid response from an upstream server.
503Service Unavailable5xxThe server is not ready to handle the request (overloaded or down for maintenance).
504Gateway Timeout5xxThe server did not receive a timely response from an upstream server.
507Insufficient Storage5xxThe server is unable to store the representation needed to complete the request.