HTTP Status Code Lookup
Search or browse common HTTP status codes, grouped by category, with a plain-language explanation of each.
Continue · Informational
The server has received the request headers and the client should proceed to send the body.
Switching Protocols · Informational
The server is switching protocols as requested by the client (e.g. to WebSocket).
OK · Success
The request succeeded.
Created · Success
The request succeeded and a new resource was created as a result.
Accepted · Success
The request was accepted for processing, but processing isn't complete.
No Content · Success
The request succeeded but there's no content to return.
Partial Content · Success
Returning only part of the resource, used for range requests like resumable downloads.
Moved Permanently · Redirection
The resource has permanently moved to a new URL, given in the Location header.
Found · Redirection
The resource temporarily lives at a different URL. Historically often misused for permanent redirects.
Not Modified · Redirection
The cached version is still valid; no need to re-transfer the resource.
Temporary Redirect · Redirection
Like 302, but guarantees the request method won't change on redirect.
Permanent Redirect · Redirection
Like 301, but guarantees the request method won't change on redirect.
Bad Request · Client Error
The server couldn't understand the request due to invalid syntax.
Unauthorized · Client Error
Authentication is required and has either failed or not been provided.
Forbidden · Client Error
The server understood the request but refuses to authorize it.
Not Found · Client Error
The server can't find the requested resource.
Method Not Allowed · Client Error
The request method is known but not supported for this resource.
Request Timeout · Client Error
The server timed out waiting for the request.
Conflict · Client Error
The request conflicts with the current state of the resource.
Gone · Client Error
The resource is permanently gone and won't come back, unlike 404.
Payload Too Large · Client Error
The request body is larger than the server is willing to process.
Unsupported Media Type · Client Error
The request's content type isn't supported by the server.
I'm a Teapot · Client Error
An April Fools' joke from RFC 2324, occasionally used by APIs as an easter egg.
Unprocessable Entity · Client Error
The request is well-formed but contains semantic errors.
Too Many Requests · Client Error
The client has sent too many requests in a given time (rate limiting).
Internal Server Error · Server Error
A generic error indicating something went wrong on the server.
Not Implemented · Server Error
The server doesn't support the functionality required to fulfill the request.
Bad Gateway · Server Error
A server acting as a gateway received an invalid response from an upstream server.
Service Unavailable · Server Error
The server isn't ready to handle the request, often due to overload or maintenance.
Gateway Timeout · Server Error
A server acting as a gateway didn't get a response in time from an upstream server.
Frequently asked questions
What's the difference between a 401 and a 403?+
401 means you haven't proven who you are yet (missing or invalid credentials). 403 means the server knows exactly who you are and is refusing anyway, you're authenticated but not authorized for this specific thing.
When should an API return 404 vs. 400?+
404 means the specific resource (like a record with that ID) doesn't exist. 400 means the request itself was malformed, wrong data type, missing required field, before the server even tries to look anything up.
What's the difference between 502 and 504?+
Both involve a server acting as a gateway or proxy. 502 means it got back an invalid or garbled response from the upstream server. 504 means it didn't get a response in time at all, a timeout.