HTTP Status Code Explorer

The server received the initial request headers and is ready for the request body.

Common usage: Large upload begins only after the server confirms it can continue.

The server accepts changing to a different protocol requested by the client.

Common usage: HTTP connection upgrades to WebSocket for real-time events.

The request succeeded and the server returned the expected response.

Common usage: GET /users/123 returns a user object successfully.

A new resource was created as a result of the request.

Common usage: POST /users creates a user and returns its id.

The request was accepted for processing, but work has not completed yet.

Common usage: Export job is queued and will finish asynchronously.

The request succeeded, but there is no response body to return.

Common usage: DELETE /users/123 succeeds without returning JSON.

The resource has a permanent new URL and clients should update links.

Common usage: Old endpoint permanently redirects to a new versioned endpoint.

The resource is temporarily available at a different URL.

Common usage: Temporary redirect to a maintenance or login route.

Cached content is still valid, so the server does not resend the full response.

Common usage: Client sends If-None-Match and keeps existing cached payload.

The request is malformed or fails validation rules.

Common usage: JSON payload misses required fields or has invalid types.

Authentication is required or the provided credentials are invalid.

Common usage: Request is missing a bearer token or token is expired.

The client is authenticated but does not have permission for this action.

Common usage: Regular user attempts an admin-only operation.

The requested resource could not be found.

Common usage: GET /projects/999 returns no matching project.

The endpoint exists but does not support the HTTP method used.

Common usage: POST sent to a route that only allows GET.

The request conflicts with the current state of the resource.

Common usage: Attempting to create a user with an email that already exists.

The request format is valid, but semantic validation failed.

Common usage: Date range is logically invalid even though JSON is valid.

The client exceeded the allowed request rate limit.

Common usage: Too many login attempts in a short time period.

An unexpected server-side error occurred while processing the request.

Common usage: Unhandled exception in the API handler.

The server does not support the functionality required for this request.

Common usage: Endpoint exists in docs but is not implemented yet.

A gateway/proxy received an invalid response from an upstream server.

Common usage: API gateway cannot get a valid response from a microservice.

The server is temporarily unable to handle the request.

Common usage: Service is down for maintenance or overloaded.

A gateway/proxy did not receive a timely response from upstream.

Common usage: Upstream service timed out before responding.