100Continue
The server received the request headers; the client should send the body.
101Switching Protocols
The server is switching protocols as requested, e.g. upgrading to WebSocket.
103Early Hints
Lets the browser start preloading resources before the final response.
200OK
The request succeeded.
201Created
A new resource was created; the Location header usually points to it.
Tip: Return this from POST endpoints that create things.
202Accepted
The request was accepted for processing, which hasn't finished yet.
204No Content
Success with no response body.
Tip: Common for DELETE and for PUT/PATCH that don't return the resource.
206Partial Content
Only part of the resource is returned, in answer to a Range request (e.g. video streaming).
301Moved Permanently
The resource has a new permanent URL.
Tip: Use for SEO-safe permanent redirects; browsers may change POST to GET — use 308 to keep the method.
302Found
Temporary redirect to another URL.
303See Other
Redirect the client to another URL using GET — typical after a form POST.
304Not Modified
The cached copy is still valid; no body is sent.
Tip: Triggered by If-None-Match / If-Modified-Since.
307Temporary Redirect
Temporary redirect that keeps the original method and body.
308Permanent Redirect
Permanent redirect that keeps the original method and body.
400Bad Request
The server can't process the request because it's malformed (bad JSON, missing fields…).
401Unauthorized
Authentication is required or failed. The response should include WWW-Authenticate.
Tip: Means “not logged in”. Logged in but not allowed is 403.
402Payment Required
Reserved; some APIs use it when a paid plan or credit is required.
403Forbidden
The server understood the request but refuses it — the client lacks permission.
404Not Found
No resource exists at this URL.
405Method Not Allowed
The URL exists but doesn't support this HTTP method; see the Allow header.
406Not Acceptable
The server can't produce a response matching the Accept headers.
408Request Timeout
The server timed out waiting for the request.
409Conflict
The request conflicts with the current state, e.g. a duplicate or an edit conflict.
410Gone
The resource was deliberately removed and won't return.
Tip: Search engines drop 410 pages faster than 404s.
411Length Required
The server requires a Content-Length header.
412Precondition Failed
A condition in headers like If-Match wasn't met.
413Content Too Large
The request body is bigger than the server allows.
414URI Too Long
The URL is longer than the server will handle.
415Unsupported Media Type
The body's Content-Type isn't supported, e.g. sending form data to a JSON-only API.
416Range Not Satisfiable
The requested Range is outside the resource.
418I'm a teapot
An April Fools' joke code (RFC 2324); sometimes used for fun or to reject bots.
421Misdirected Request
The request reached a server that can't respond for this host.
422Unprocessable Content
The body is well-formed but has semantic errors, such as failed validation.
423Locked
The resource is locked (WebDAV).
425Too Early
The server won't process a request that might be replayed (TLS early data).
426Upgrade Required
The client must switch to a different protocol.
428Precondition Required
The server requires a conditional request to prevent lost updates.
429Too Many Requests
Rate limit exceeded. Check the Retry-After header.
Tip: Back off exponentially before retrying.
431Request Header Fields Too Large
Headers (often cookies) are too large.
451Unavailable For Legal Reasons
Access is blocked for legal reasons, e.g. a court order.
500Internal Server Error
A generic server error — something broke while handling the request.
Tip: Check the server logs; never expose stack traces to users.
501Not Implemented
The server doesn't support the functionality required.
502Bad Gateway
A proxy or gateway got an invalid response from the upstream server.
Tip: Often means your app process crashed or isn't listening behind the proxy.
503Service Unavailable
The server is overloaded or down for maintenance; Retry-After may say when to retry.
504Gateway Timeout
A proxy or gateway didn't get a response from upstream in time.
505HTTP Version Not Supported
The server doesn't support the HTTP version used.
507Insufficient Storage
The server can't store what's needed to complete the request.
508Loop Detected
The server found an infinite loop while processing (WebDAV).
511Network Authentication Required
You need to log in to the network, e.g. a hotel Wi-Fi captive portal.