HTTP Status Code Reference

The initial request was received and the client can continue.

Typical usage: Used during large request uploads before sending the body.

The server is switching to a different protocol.

Typical usage: Common in WebSocket upgrade handshakes.

The request succeeded.

Typical usage: Standard response for successful page loads and API reads.

The request succeeded and created a new resource.

Typical usage: Returned after successful form submissions or POST requests.

The request was accepted but processing is not complete.

Typical usage: Useful for queued jobs and async API workflows.

The request succeeded with no response body.

Typical usage: Common for successful deletes or silent updates.

The resource has a permanent new URL.

Typical usage: Use for durable SEO redirects after URL changes.

The resource is temporarily available at another URL.

Typical usage: Use for short-lived redirects and temporary routing.

The cached client copy is still valid.

Typical usage: Used with conditional requests and browser caching.

Temporary redirect that preserves the original method.

Typical usage: Useful when POST or PUT requests must not become GET requests.

Permanent redirect that preserves the original method.

Typical usage: Use for permanent API or form endpoint moves.

The server could not understand the request.

Typical usage: Return for malformed input or invalid request syntax.

Authentication is required or failed.

Typical usage: Use when a login, token, or credential is missing or invalid.

The server understood the request but refuses access.

Typical usage: Use when the user is known but lacks permission.

The requested resource could not be found.

Typical usage: Return for missing pages, records, and routes.

The resource does not support the HTTP method.

Typical usage: Return when POST, PUT, or DELETE is not allowed.

The request conflicts with current resource state.

Typical usage: Use for duplicate records or edit conflicts.

The resource used to exist but is intentionally removed.

Typical usage: Useful for SEO when content is permanently retired.

An April Fools status code from RFC 2324.

Typical usage: Mostly used as an easter egg or test response.

The client sent too many requests in a given time.

Typical usage: Use for rate limits and abuse protection.

The server hit an unexpected failure.

Typical usage: Generic fallback for unhandled server errors.

A gateway received an invalid upstream response.

Typical usage: Common with reverse proxies and upstream service failures.

The server is temporarily unable to handle the request.

Typical usage: Use during maintenance, overload, or temporary outages.

A gateway timed out waiting for an upstream response.

Typical usage: Common when backend services are slow or unavailable.