HTTP Status Codes

Searchable reference of HTTP response status codes and their meanings.

How it works

Search HTTP status codes by number or keyword to recall what 404, 502, or 429 mean in production. Includes common REST and proxy responses.

Example: search 404 to find “Not Found”, or type a keyword like timeout.

100
Continue
Request received, continue sending the body.
101
Switching Protocols
Server is switching protocols as requested.
200
OK
The request succeeded.
201
Created
Request succeeded and a new resource was created.
202
Accepted
Request accepted for processing, not yet completed.
204
No Content
Success, but there is no body to return.
206
Partial Content
Partial response delivered for a range request.
301
Moved Permanently
Resource permanently moved to a new URL.
302
Found
Resource temporarily at a different URL.
304
Not Modified
Cached version is still valid.
307
Temporary Redirect
Repeat the request to a new URL, keep the method.
308
Permanent Redirect
Permanent redirect, keep the method.
400
Bad Request
The server could not understand the request.
401
Unauthorized
Authentication is required or failed.
403
Forbidden
Authenticated but not allowed to access.
404
Not Found
The requested resource does not exist.
405
Method Not Allowed
HTTP method is not supported for this resource.
408
Request Timeout
The server timed out waiting for the request.
409
Conflict
Request conflicts with the current server state.
410
Gone
The resource is permanently unavailable.
413
Payload Too Large
The request body is larger than allowed.
415
Unsupported Media Type
The payload format is not supported.
418
I'm a teapot
Refuses to brew coffee with a teapot (RFC 2324).
422
Unprocessable Entity
Semantic errors prevented processing.
429
Too Many Requests
Rate limit exceeded, slow down.
500
Internal Server Error
A generic server-side error occurred.
501
Not Implemented
The server does not support the functionality.
502
Bad Gateway
Invalid response from an upstream server.
503
Service Unavailable
Server is overloaded or down for maintenance.
504
Gateway Timeout
Upstream server failed to respond in time.