HTTP Status Codes Reference
Complete reference of HTTP status codes with descriptions and use cases.
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The server is switching protocols as requested by the client.
Processing
The server has received and is processing the request, but no response is available yet.
Early Hints
Used to return some response headers before final HTTP message.
OK
The request succeeded. The meaning depends on the HTTP method used.
Created
The request succeeded and a new resource was created.
Accepted
The request has been received but not yet acted upon.
No Content
The request succeeded but returns no message body.
Partial Content
The server is delivering only part of the resource due to a range header.
Moved Permanently
The URL of the requested resource has been changed permanently.
Found
The URI of requested resource has been changed temporarily.
See Other
The response can be found under a different URI using GET.
Not Modified
The resource has not been modified since the last request.
Temporary Redirect
The request should be repeated with another URI, but future requests should still use the original URI.
Permanent Redirect
The resource is now permanently located at another URI.
Bad Request
The server cannot process the request due to client error (malformed syntax, invalid request).
Unauthorized
Authentication is required and has failed or has not been provided.
Forbidden
The server understood the request but refuses to authorize it.
Not Found
The server cannot find the requested resource.
Method Not Allowed
The request method is not supported for the requested resource.
Conflict
The request conflicts with the current state of the server.
Gone
The requested content has been permanently deleted from server.
Unprocessable Entity
The request was well-formed but semantically incorrect.
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Internal Server Error
The server has encountered a situation it does not know how to handle.
Not Implemented
The request method is not supported by the server.
Bad Gateway
The server got an invalid response from an upstream server.
Service Unavailable
The server is not ready to handle the request (overloaded or down for maintenance).
Gateway Timeout
The server is acting as a gateway and cannot get a response in time.