HTTP Status Code Reference
Browse all HTTP status codes with descriptions and use cases.
Search HTTP Status Codes
Status Codes
About the HTTP Status Code Reference
The HTTP Status Reference lists the status codes a server can return, with what each one means and when to use it. Search by number or by keyword such as auth, redirect or timeout.
Codes are grouped in hundreds. 1xx means the request is still being processed, 2xx means success, 3xx means a redirect or a cached copy, 4xx means the client did something wrong, and 5xx means the server failed. The first digit tells you whose problem it is before you read the rest.
Two pairs are worth knowing by heart. 401 means you are not authenticated, 403 means you are authenticated but not allowed. 301 is a permanent redirect that browsers and search engines cache, 302 is temporary; getting them the wrong way round can leave a stale redirect in place for months.
Common questions about HTTP Status Reference
What do the first digits mean?
1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error.
What is the difference between 401 and 403?
401 means authentication is missing or failed. 403 means the identity is known but does not have permission.
301 or 302 for a redirect?
301 is permanent and gets cached by browsers and search engines. 302 is temporary. Use 301 only when the move really is permanent.
What is 429?
Too many requests: the client is being rate limited and should slow down or back off.
What does 204 mean?
Success with no content in the body, common for a successful DELETE or an update with nothing to return.
Is 418 a real code?
It exists as an April Fools joke that was formally reserved. Do not use it in production APIs.