The server has received the request headers and the client should proceed to send the request body.
The requester has asked the server to switch protocols and the server has agreed.
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.
The request has succeeded. The meaning of success depends on the HTTP method.
The request has succeeded and a new resource has been created as a result.
The request has been accepted for processing, but the processing has not been completed.
The returned metadata is not exactly the same as is available from the origin server.
The server successfully processed the request and is not returning any content.
The server successfully processed the request, but requires the requester to reset the document view.
The server is delivering only part of the resource due to a range header sent by the client.
This and all future requests should be directed to the given URI.
The target resource resides temporarily under a different URI.
The response to the request can be found under another URI using the GET method.
Indicates that the resource has not been modified since the version specified by request headers.
The target resource resides temporarily under a different URI. The method should NOT change.
The target resource has been definitively moved. The method should NOT change.
The server cannot process the request due to a client error (malformed syntax, invalid message, etc.).
Authentication is required and has failed or not been provided.
Reserved for future use. Some services use this for payment-related restrictions.
The server understood the request but refuses to authorize it.
The server cannot find the requested resource. The URL is not recognized.
The request method is known by the server but is not supported by the target resource.
The server would like to shut down this unused connection.
The request conflicts with the current state of the server.
Access to the target resource is no longer available and this condition is likely to be permanent.
The request body is larger than the server is willing or able to process.
The media format of the requested data is not supported by the server.
The server refuses the attempt to brew coffee with a teapot. (RFC 2324 April Fools' joke)
The request was well-formed but was unable to be followed due to semantic errors.
The user has sent too many requests in a given amount of time (rate limiting).
The server is unwilling to process the request because its header fields are too large.
The server is denying access to the resource as a consequence of a legal demand.
The server has encountered a situation it does not know how to handle.
The request method is not supported by the server and cannot be handled.
The server, while acting as a gateway, received an invalid response from the upstream server.
The server is not ready to handle the request. Common causes: down for maintenance or overloaded.
The server is acting as a gateway and cannot get a response in time from the upstream server.
The HTTP version used in the request is not supported by the server.
Complete HTTP Status Code Reference
Searchable reference for all standard HTTP status codes. Find the meaning, typical use case, and debugging tips for any response code from 100 to 599. Essential for API development, debugging network issues, and understanding server responses.