HTTP Status Code Reference
Search or browse every common HTTP status code, from 1xx informational through 5xx server errors, with a plain-English explanation of what each one means.
Continue · 1xx Informational
The initial part of the request has been received; the client should continue with the rest.
Switching Protocols · 1xx Informational
The server agrees to switch protocols, as requested by the client (e.g. to WebSocket).
OK · 2xx Success
The request succeeded, and the response contains the requested data.
Created · 2xx Success
The request succeeded and a new resource was created as a result.
Accepted · 2xx Success
The request was accepted for processing, but processing isn't complete yet.
No Content · 2xx Success
The request succeeded, but there's no content to send in the response.
Partial Content · 2xx Success
Only part of the resource is being returned, as requested via a Range header.
Moved Permanently · 3xx Redirection
The resource has permanently moved to a new URL, given in the Location header.
Found · 3xx Redirection
The resource temporarily resides at a different URL. Historically often misused for 303-style redirects.
See Other · 3xx Redirection
The response to the request can be found at another URL using a GET request.
Not Modified · 3xx Redirection
The resource hasn't changed since the version specified by request headers; use the cached copy.
Temporary Redirect · 3xx Redirection
Like 302, but guarantees the method and body of the original request are preserved.
Permanent Redirect · 3xx Redirection
Like 301, but guarantees the method and body of the original request are preserved.
Bad Request · 4xx Client Error
The server couldn't understand the request due to invalid syntax.
Unauthorized · 4xx Client Error
Authentication is required and has either failed or not been provided.
Payment Required · 4xx Client Error
Reserved for future use; occasionally used by APIs to signal billing issues.
Forbidden · 4xx Client Error
The client's identity is known, but it doesn't have permission to access the resource.
Not Found · 4xx Client Error
The server can't find the requested resource.
Method Not Allowed · 4xx Client Error
The request method is known but not supported by this particular resource.
Not Acceptable · 4xx Client Error
No content matching the criteria in the request's Accept headers is available.
Request Timeout · 4xx Client Error
The server timed out waiting for the request from the client.
Conflict · 4xx Client Error
The request conflicts with the current state of the target resource.
Gone · 4xx Client Error
The resource previously existed but has been permanently removed, with no forwarding address.
Length Required · 4xx Client Error
The request didn't specify the length of its content, which is required.
Payload Too Large · 4xx Client Error
The request body is larger than the server is willing or able to process.
URI Too Long · 4xx Client Error
The requested URL is longer than the server is willing to interpret.
Unsupported Media Type · 4xx Client Error
The request's content type isn't supported by the server.
I'm a Teapot · 4xx Client Error
An April Fools' joke from RFC 2324 (Hyper Text Coffee Pot Control Protocol); not meant to be used seriously.
Unprocessable Entity · 4xx Client Error
The request is well-formed but contains semantic errors (common for validation failures in APIs).
Too Early · 4xx Client Error
The server is unwilling to risk processing a request that might be replayed.
Too Many Requests · 4xx Client Error
The client has sent too many requests in a given time and is being rate-limited.
Request Header Fields Too Large · 4xx Client Error
The server won't process the request because its headers are too large.
Unavailable For Legal Reasons · 4xx Client Error
The resource is unavailable due to a legal demand, such as government censorship.
Internal Server Error · 5xx Server Error
A generic error indicating the server encountered an unexpected condition.
Not Implemented · 5xx Server Error
The server doesn't support the functionality required to fulfill the request.
Bad Gateway · 5xx Server Error
A server acting as a gateway or proxy got an invalid response from the upstream server.
Service Unavailable · 5xx Server Error
The server isn't ready to handle the request, often due to maintenance or overload.
Gateway Timeout · 5xx Server Error
A gateway or proxy didn't get a response from the upstream server in time.
HTTP Version Not Supported · 5xx Server Error
The HTTP version used in the request isn't supported by the server.
Insufficient Storage · 5xx Server Error
The server can't store the representation needed to complete the request (WebDAV).
Network Authentication Required · 5xx Server Error
The client needs to authenticate to gain network access, common on captive portals.
Frequently asked questions
What's the difference between a 401 and a 403?+
401 Unauthorized means authentication is missing or failed; 403 Forbidden means the server knows who you are but you don't have permission to access that resource.
Is 418 "I'm a Teapot" a real status code?+
It's a real, officially registered status code, but it originated as an April Fools' joke in RFC 2324 and isn't meant to be used in serious production APIs.
What should I do about a 429 Too Many Requests error?+
Slow down your request rate and respect any Retry-After header in the response; it means you've hit a rate limit and the server is asking you to back off.