HTTP Status Codes
A searchable reference of HTTP status codes with meanings and when to use them.
- 100 Continue Informational
The server received the request headers; continue sending the body.
- 101 Switching Protocols Informational
The server is switching protocols as requested (e.g. to WebSocket).
- 200 OK Success
The request succeeded.
- 201 Created Success
The request succeeded and a new resource was created.
- 202 Accepted Success
The request was accepted for processing but isn't complete.
- 204 No Content Success
Success, but there's no content to return.
- 206 Partial Content Success
The server is delivering part of the resource (range request).
- 301 Moved Permanently Redirection
The resource has permanently moved to a new URL (SEO-friendly redirect).
- 302 Found Redirection
The resource is temporarily at a different URL.
- 303 See Other Redirection
Fetch the resource from another URL with a GET request.
- 304 Not Modified Redirection
The cached version is still valid; nothing changed.
- 307 Temporary Redirect Redirection
Temporary redirect that preserves the HTTP method.
- 308 Permanent Redirect Redirection
Permanent redirect that preserves the HTTP method.
- 400 Bad Request Client error
The server couldn't understand the request (malformed syntax).
- 401 Unauthorized Client error
Authentication is required and has failed or not been provided.
- 402 Payment Required Client error
Reserved for future use; sometimes used by payment APIs.
- 403 Forbidden Client error
You're authenticated but not allowed to access this resource.
- 404 Not Found Client error
The requested resource doesn't exist.
- 405 Method Not Allowed Client error
The HTTP method isn't supported for this resource.
- 406 Not Acceptable Client error
No representation matches the Accept headers.
- 408 Request Timeout Client error
The server timed out waiting for the request.
- 409 Conflict Client error
The request conflicts with the current state of the resource.
- 410 Gone Client error
The resource is permanently gone.
- 413 Payload Too Large Client error
The request body is larger than the server will accept.
- 415 Unsupported Media Type Client error
The request's media type isn't supported.
- 418 I'm a teapot Client error
An April Fools' joke status — the server refuses to brew coffee.
- 422 Unprocessable Entity Client error
The request was well-formed but has semantic errors (validation).
- 429 Too Many Requests Client error
You've sent too many requests (rate limited).
- 451 Unavailable For Legal Reasons Client error
Access denied for legal reasons.
- 500 Internal Server Error Server error
A generic server-side error occurred.
- 501 Not Implemented Server error
The server doesn't support the functionality required.
- 502 Bad Gateway Server error
An upstream server returned an invalid response.
- 503 Service Unavailable Server error
The server is overloaded or down for maintenance.
- 504 Gateway Timeout Server error
An upstream server didn't respond in time.
- 505 HTTP Version Not Supported Server error
The HTTP version used isn't supported.
No status codes match your search.
How to use the HTTP Status Codes
-
Search by number or keyword.
-
Read the meaning.
-
Use the right code in your API.
HTTP status codes explained
HTTP status codes tell clients the outcome of a request — success, redirect, client error or server error. Remembering them all is hard. This searchable reference lists every standard code grouped by class (1xx–5xx) with a plain explanation of what it means and when to return it.
Key features
- Every standard 1xx–5xx code
- Plain-language meanings
- Filter by class or search
- Quick copy of code & name
Frequently asked questions
What's the difference between 401 and 403?
401 Unauthorized means you're not authenticated; 403 Forbidden means you're authenticated but not allowed.
When should I use 301 vs 302?
301 is a permanent redirect (SEO passes value); 302 is temporary. Use 301 for moved pages.
Is 418 real?
Yes — 418 'I'm a teapot' is a real, if whimsical, status from an April Fools' RFC.