Skip to content
Network & Email Runs in your browser — nothing uploadedFree · No signup

HTTP Status Codes — Complete Reference

A searchable reference of HTTP response status codes with practical explanations for API developers — what each code means, when to return it, and what usually causes it.

1xx Informational

100Continue
The server received the request headers; the client should send the body. Used with Expect: 100-continue.
101Switching Protocols
The server is switching protocols as requested, e.g. upgrading HTTP to WebSocket.
103Early Hints
Lets the browser preload resources (Link headers) while the server prepares the final response.

2xx Success

200OK
Standard success. GET returns the resource; POST returns the result of the action.
201Created
A new resource was created. Return a Location header pointing to it — typical for POST.
202Accepted
Request accepted for asynchronous processing that hasn't finished yet (queues, background jobs).
204No Content
Success with no response body — common for DELETE or PUT.
206Partial Content
The server is returning a byte range (Range header) — used for video/audio streaming and resumable downloads.

3xx Redirection

301Moved Permanently
The resource has a new permanent URL. Search engines transfer ranking to the new URL.
302Found
Temporary redirect. Browsers may change POST to GET when following it.
303See Other
Redirect the client to another URL using GET — e.g. after a form POST.
304Not Modified
The cached version is still valid (ETag / If-Modified-Since). No body is sent.
307Temporary Redirect
Temporary redirect that preserves the HTTP method and body.
308Permanent Redirect
Permanent redirect that preserves the HTTP method and body.

4xx Client error

400Bad Request
The request is malformed — invalid JSON, missing required parameters, wrong types.
401Unauthorized
Authentication is missing or invalid. The client should log in or refresh its token.
402Payment Required
Reserved; sometimes used by APIs when a plan limit or payment is required.
403Forbidden
The client is authenticated but not allowed to access this resource.
404Not Found
No resource exists at this URL. Also used to hide resources from unauthorized users.
405Method Not Allowed
The HTTP method isn't supported for this endpoint. Include an Allow header.
406Not Acceptable
The server can't produce a response matching the Accept headers.
408Request Timeout
The client took too long to send the request.
409Conflict
The request conflicts with the current state — duplicate records, edit conflicts, version mismatch.
410Gone
The resource was deliberately removed and won't return. Search engines drop it faster than 404.
411Length Required
The server requires a Content-Length header.
412Precondition Failed
A conditional header (If-Match, If-Unmodified-Since) didn't match — used for optimistic locking.
413Content Too Large
The request body exceeds the server's limit (e.g. Nginx client_max_body_size).
414URI Too Long
The URL is longer than the server will process.
415Unsupported Media Type
The Content-Type isn't supported — e.g. sending form data to a JSON-only endpoint.
416Range Not Satisfiable
The requested byte range is outside the file size.
418I'm a teapot
An April Fools' joke from RFC 2324. Some APIs use it playfully.
422Unprocessable Content
The request is well-formed but fails validation rules — common in REST and Laravel/Rails/FastAPI APIs.
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, e.g. TLS or HTTP/2.
428Precondition Required
The server requires conditional requests to prevent lost updates.
429Too Many Requests
Rate limit exceeded. Respect the Retry-After header and back off.
431Request Header Fields Too Large
Headers (often cookies) are too large.
451Unavailable For Legal Reasons
Blocked for legal reasons, such as a court order or regional law.

5xx Server error

500Internal Server Error
An unhandled exception on the server. Check server logs — the client can't fix this.
501Not Implemented
The server doesn't support the functionality required.
502Bad Gateway
A proxy (Nginx, load balancer, Cloudflare) got an invalid response from the upstream app — often the app crashed or isn't running.
503Service Unavailable
The server is overloaded or in maintenance. Use Retry-After.
504Gateway Timeout
The proxy didn't get a response from upstream in time — slow queries or long-running requests.
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
Infinite loop detected while processing (WebDAV).
511Network Authentication Required
The client must authenticate to gain network access — captive portals on public Wi-Fi.

How to use the HTTP Status Codes

  1. Type a code or keyword in the search box.
  2. Filter by class (2xx, 4xx…).
  3. Click a code to copy it.

Features

  • All standard 1xx–5xx codes
  • Search by number or keyword
  • Filter by class
  • Developer notes for common confusions

Frequently asked questions

401 vs 403 — what's the difference?

401 Unauthorized means the request has no valid authentication — log in and retry. 403 Forbidden means you are authenticated but not allowed to access the resource.

Should validation errors return 400 or 422?

Both are used. 400 is for malformed requests; 422 Unprocessable Content is common for well-formed requests that fail validation rules.