HTTP Status Code Lookup
Complete reference for HTTP status codes with descriptions and examples
Continue
The server has received the request headers and the client should proceed to send the request body.
Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
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 has succeeded. The meaning of the success depends on the HTTP method.
Example: GET request for a resource that exists
Created
The request has been fulfilled and resulted in a new resource being created.
Example: POST request that creates a new user
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The server successfully processed the request, but is returning information from another source.
No Content
The server successfully processed the request and is not returning any content.
Example: DELETE request that removes a resource
Reset Content
The server successfully processed the request, but is not returning any content, and requires that the requester reset the document view.
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
Multiple Choices
The request has more than one possible response. The user agent should choose one of them.
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
Example: Website moved to new domain
Found
The URI of requested resource has been changed temporarily. Further changes in the URI might be made in the future.
See Other
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
Not Modified
The client has performed a conditional GET request and access is allowed, but the document has not been modified.
Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request.
Permanent Redirect
The resource is now permanently located at another URI, specified by the Location: header.
Bad Request
The server could not understand the request due to invalid syntax.
Example: Malformed JSON in request body
Unauthorized
The client must authenticate itself to get the requested response.
Example: Missing or invalid authentication token
Payment Required
This response code is reserved for future use. Initial aim for creating this code was using it for digital payment systems.
Forbidden
The client does not have access rights to the content, so the server is refusing to give the requested resource.
Example: User lacks permission to access resource
Not Found
The server can not find the requested resource. This is probably the most famous status code due to its frequent occurrence on the web.
Example: Requested page or API endpoint does not exist
Method Not Allowed
The request method is known by the server but has been disabled and cannot be used.
Example: POST request to a GET-only endpoint
Not Acceptable
The target resource does not have a current representation that would be acceptable to the user agent.
Proxy Authentication Required
The client must first authenticate itself with the proxy.
Request Timeout
The server would like to shut down this unused connection.
Conflict
The request conflicts with the current state of the server.
Example: Trying to create resource that already exists
Gone
The requested resource is no longer available at the server and no forwarding address is known.
Length Required
The server refuses to accept the request without a defined Content-Length.
Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
Payload Too Large
Request entity is larger than limits defined by server.
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
Unsupported Media Type
The media format of the requested data is not supported by the server.
Range Not Satisfiable
The range specified by the Range header field in the request cannot be fulfilled.
Expectation Failed
The expectation indicated by the Expect request header field cannot be met by the server.
I'm a teapot
The server refuses the attempt to brew coffee with a teapot.
Example: April Fools' joke from 1998
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Locked
The resource that is being accessed is locked.
Failed Dependency
The request failed because it depended on another request and that request failed.
Too Early
Indicates that the server is unwilling to risk processing a request that might be replayed.
Upgrade Required
The server refuses to perform the request using the current protocol.
Precondition Required
The origin server requires the request to be conditional.
Too Many Requests
The user has sent too many requests in a given amount of time.
Example: Rate limiting exceeded
Request Header Fields Too Large
The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.
Unavailable For Legal Reasons
The user agent requested a resource that cannot legally be provided.
Internal Server Error
The server has encountered a situation it does not know how to handle.
Example: Unhandled exception in server code
Not Implemented
The request method is not supported by the server and cannot be handled.
Bad Gateway
The server, while working as a gateway to get a response needed to handle the request, got an invalid response.
Example: Upstream server returned invalid response
Service Unavailable
The server is not ready to handle the request.
Example: Server maintenance or overload
Gateway Timeout
The server is acting as a gateway and cannot get a response in time.
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
Variant Also Negotiates
The server has an internal configuration error.
Insufficient Storage
The server is unable to store the representation needed to complete the request.
Loop Detected
The server detected an infinite loop while processing the request.
Not Extended
Further extensions to the request are required for the server to fulfill it.
Network Authentication Required
The client needs to authenticate to gain network access.