HTTP Status Code Reference
A quick reference guide for HTTP status codes. Search by code, name, or description.
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.
Created
The request has been fulfilled, resulting in the creation of a new resource.
Accepted
The request has been accepted for processing, but the processing has not been completed.
Non-Authoritative Information
The server is a transforming proxy that received a 200 OK from its origin, but is returning a modified version of the origin's response.
No Content
The server successfully processed the request and is not returning any content.
Reset Content
The server successfully processed the request, but is not returning any content. The user agent should 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 or user 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.
Found
The URI of requested resource has been changed temporarily.
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
Used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.
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: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used.
Bad Request
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax).
Unauthorized
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". The client must authenticate itself to get the requested response.
Payment Required
This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.
Forbidden
The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client's identity is known to the server.
Not Found
The server can not find the requested resource. In an browser, this means the URL is not recognized.
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
Not Acceptable
The server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers.
Proxy Authentication Required
This is similar to 401 but authentication is needed to be done by a proxy.
Request Timeout
This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection.
Conflict
This response is sent when a request conflicts with the current state of the server.
Gone
This response is sent when the requested content has been permanently deleted from server, with no forwarding address.
Length Required
Server rejected the request because the Content-Length header field is not defined and the server requires it.
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, so the server is rejecting the request.
Range Not Satisfiable
The range specified by the Range header field in the request cannot be fulfilled.
Expectation Failed
This response code means the expectation indicated by the Expect request header field could not be met by the server.
I'm a teapot
The server refuses the attempt to brew coffee with a teapot.
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Too Many Requests
The user has sent too many requests in a given amount of time ("rate limiting").
Unavailable For Legal Reasons
The user-agent requested a resource that cannot legally be provided, such as a web page censored by a government.
Internal Server Error
The server has encountered a situation it doesn't know how to handle.
Not Implemented
The request method is not supported by the server and cannot be handled.
Bad Gateway
This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.
Service Unavailable
The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.
Gateway Timeout
This error response is given when 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.
Network Authentication Required
Indicates that the client needs to authenticate to gain network access.