๐ก HTTP Status Code Reference
CodeNameDescription
100ContinueThe initial part of the request has been received and the client should continue with the request.
101Switching ProtocolsThe server is switching protocols as requested by the client via the Upgrade header.
102ProcessingThe server has received and is processing the request, but no response is available yet (WebDAV).
103Early HintsUsed to return some response headers before the final HTTP message, e.g. for preloading resources.
200OKThe request has succeeded.
201CreatedThe request has succeeded and a new resource has been created as a result.
202AcceptedThe request has been received but not yet acted upon.
203Non-Authoritative InformationThe returned metadata is not exactly the same as from the origin server, but from a local or third-party copy.
204No ContentThere is no content to send for this request, but the headers are useful.
205Reset ContentTells the client to reset the document that sent this request.
206Partial ContentUsed when the Range header is sent to only retrieve part of a resource.
207Multi-StatusConveys information about multiple resources for situations where multiple status codes are appropriate (WebDAV).
208Already ReportedUsed inside a DAV: propstat response element to avoid repeatedly enumerating internal members (WebDAV).
226IM UsedThe server has fulfilled a GET request and the response is a representation of the result of instance manipulations.
300Multiple ChoicesThe request has more than one possible response and the client should choose one.
301Moved PermanentlyThe URL of the requested resource has been changed permanently.
302FoundThe URI of requested resource has been changed temporarily.
303See OtherThe server sends this response to direct the client to get the requested resource at another URI with a GET request.
304Not ModifiedTells the client that the response has not been modified, so the client can continue to use the cached version.
305Use ProxyDefined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. Deprecated.
307Temporary RedirectThe server sends this response to direct the client to get the requested resource at another URI with the same method used.
308Permanent RedirectThis means that the resource is now permanently located at another URI, specified by the Location response header.
400Bad RequestThe server cannot or will not process the request due to something that is perceived to be a client error.
401UnauthorizedThe client must authenticate itself to get the requested response.
402Payment RequiredReserved for future use, e.g. digital payment systems.
403ForbiddenThe client does not have access rights to the content, so the server is refusing to give the requested resource.
404Not FoundThe server cannot find the requested resource.
405Method Not AllowedThe request method is known by the server but is not supported by the target resource.
406Not AcceptableThe server cannot produce a response matching the list of acceptable values defined in the negotiation headers.
407Proxy Authentication RequiredSimilar to 401 but authentication is needed to be done by a proxy.
408Request TimeoutThe server would like to shut down this unused connection.
409ConflictThe request conflicts with the current state of the target resource.
410GoneThe requested content has been permanently deleted from the server, with no forwarding address.
411Length RequiredThe server refuses to accept the request without a defined Content-Length header.
412Precondition FailedThe client has indicated preconditions in its headers which the server does not meet.
413Payload Too LargeThe request entity is larger than limits defined by the server.
414URI Too LongThe URI requested by the client is longer than the server is willing to interpret.
415Unsupported Media TypeThe media format of the requested data is not supported by the server.
416Range Not SatisfiableThe range specified by the Range header cannot be fulfilled.
417Expectation FailedThe expectation indicated by the Expect header field cannot be met by the server.
418I'm a teapotThe server refuses the attempt to brew coffee with a teapot (an April Fools' joke, RFC 2324).
421Misdirected RequestThe request was directed at a server that is not able to produce a response.
422Unprocessable ContentThe request was well-formed but was unable to be followed due to semantic errors.
423LockedThe resource that is being accessed is locked (WebDAV).
424Failed DependencyThe request failed due to failure of a previous request (WebDAV).
425Too EarlyIndicates that the server is unwilling to risk processing a request that might be replayed.
426Upgrade RequiredThe server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades.
428Precondition RequiredThe origin server requires the request to be conditional, to prevent lost update problems.
429Too Many RequestsThe user has sent too many requests in a given amount of time (rate limiting).
431Request Header Fields Too LargeThe server is unwilling to process the request because its header fields are too large.
451Unavailable For Legal ReasonsThe user requests a resource that cannot legally be provided, such as a web page censored by a government.
500Internal Server ErrorThe server has encountered a situation it does not know how to handle.
501Not ImplementedThe request method is not supported by the server and cannot be handled.
502Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from the upstream server.
503Service UnavailableThe server is not ready to handle the request, often due to maintenance or overload.
504Gateway TimeoutThe server is acting as a gateway and cannot get a response in time from the upstream server.
505HTTP Version Not SupportedThe HTTP version used in the request is not supported by the server.
506Variant Also NegotiatesThe server has an internal configuration error: the chosen variant resource is configured to engage in content negotiation itself.
507Insufficient StorageThe method could not be performed on the resource because the server is unable to store the representation needed (WebDAV).
508Loop DetectedThe server detected an infinite loop while processing the request (WebDAV).
510Not ExtendedFurther extensions to the request are required for the server to fulfil it.
511Network Authentication RequiredThe client needs to authenticate to gain network access.
62 codes
A searchable reference of standard HTTP status codes โ from 1xx informational to 5xx server errors โ with a short description of what each one means. Filter by category or search by code number, name, or keyword. Handy for API development, debugging, and implementing frontend error handling.
How to use
- Type a code number (e.g. 404), name (e.g. Not Found), or keyword into the search box.
- Optionally filter by category (1xx-5xx).
- Browse the list to see what each matching status code means.
FAQ
Which status codes are included?
All standard codes registered with IANA, from 100 Continue through 511 Network Authentication Required, including less common ones like 418 I'm a teapot.
Can I search by name instead of number?
Yes โ search by code (e.g. 404), name (e.g. Not Found), or keywords in the description.
Is this useful for designing API error handling?
Yes โ filter by the 4xx (client error) or 5xx (server error) category as a reference for which code to return in which situation.
Can I compare similar codes, like 301 vs. 302?
Yes โ each code's description explains its intended use, which helps when comparing redirect-related codes like 301, 302, and 307.
What if I run into an unfamiliar status code while debugging?
Just search by the code number to quickly look up its meaning โ handy when you spot an unfamiliar code in your browser dev tools or an API response.