HTTP Status Codes Reference

Complete reference of HTTP response status codes. Search by code number or description.

100Continue

Server received request headers, client should proceed to send body.

101Switching Protocols

Server is switching protocols as requested (e.g., WebSocket upgrade).

200OK

Request succeeded. Standard response for successful GET, PUT, PATCH.

201Created

Request succeeded and a new resource was created. Use for POST requests.

202Accepted

Request accepted for processing but not yet completed. Used for async operations.

204No Content

Request succeeded but no content to return. Common for DELETE requests.

206Partial Content

Server is delivering part of the resource due to a range header.

301Moved Permanently

Resource permanently moved to a new URL. Search engines update their index.

302Found (Temporary Redirect)

Resource temporarily at a different URL. Original URL should still be used.

304Not Modified

Resource has not changed since last request. Client should use cached version.

307Temporary Redirect

Like 302 but guarantees the HTTP method will not change on redirect.

308Permanent Redirect

Like 301 but guarantees the HTTP method will not change on redirect.

400Bad Request

Server cannot process the request due to client error (malformed syntax, invalid data).

401Unauthorized

Authentication required. Client must provide valid credentials (token, API key).

403Forbidden

Client is authenticated but does not have permission to access the resource.

404Not Found

Requested resource does not exist on the server. Check the URL.

405Method Not Allowed

HTTP method (GET, POST, etc.) is not supported for this endpoint.

408Request Timeout

Server timed out waiting for the client request. Try again.

409Conflict

Request conflicts with current state of the resource (e.g., duplicate entry).

410Gone

Resource permanently deleted. Unlike 404, this is intentional and permanent.

413Payload Too Large

Request body exceeds server limit. Reduce file size or data.

415Unsupported Media Type

Server does not support the Content-Type sent (e.g., sending XML to JSON-only API).

422Unprocessable Entity

Request is well-formed but contains semantic errors (validation failed).

429Too Many Requests

Rate limit exceeded. Client sent too many requests in a given time.

500Internal Server Error

Generic server error. Something unexpected went wrong. Check server logs.

501Not Implemented

Server does not support the functionality required to fulfill the request.

502Bad Gateway

Server acting as gateway received an invalid response from upstream server.

503Service Unavailable

Server is temporarily unavailable (overloaded or under maintenance).

504Gateway Timeout

Server acting as gateway did not receive a timely response from upstream.

About HTTP Status Codes

HTTP status codes are three-digit numbers returned by servers to indicate the result of a client request. They are grouped into 5 categories: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error). Understanding these codes is essential for API development, debugging, and web development.