HTTP Status Code Reference
Look up any HTTP status code instantly. Search by code number (404, 500) or keyword (not found, unauthorized). Each status code includes its official name, description, common use cases, and related codes. Covers all standard codes from 1xx Informational to 5xx Server Error.
1xx Informational
100
Continue
Server received request headers; client should proceed to send body.
101
Switching Protocols
Server is switching protocols as requested (e.g., to WebSocket).
2xx Success
200
OK
Request succeeded. Standard response for successful GET, PUT, PATCH, DELETE.
201
Created
Request succeeded and a new resource was created. Typically returned by POST.
202
Accepted
Request accepted for processing, but not yet completed. Used for async operations.
204
No Content
Request succeeded but no content to return. Common for DELETE operations.
206
Partial Content
Server is returning partial content (range request). Used for resumable downloads.
3xx Redirection
301
Moved Permanently
Resource has permanently moved to a new URL. Search engines update their links.
302
Found
Resource temporarily at a different URL. Client should continue using original URL.
304
Not Modified
Resource hasn't changed since last request. Client should use cached version.
307
Temporary Redirect
Like 302, but guarantees method and body won't change during redirect.
308
Permanent Redirect
Like 301, but guarantees method and body won't change during redirect.
4xx Client Error
400
Bad Request
Server cannot process the request due to client error (malformed syntax, invalid data).
401
Unauthorized
Authentication is required and has failed or not been provided.
403
Forbidden
Server understood the request but refuses to authorize it. Valid credentials, insufficient permissions.
404
Not Found
Requested resource could not be found. The most well-known HTTP error.
405
Method Not Allowed
HTTP method is not allowed for this resource (e.g., POST on a read-only endpoint).
408
Request Timeout
Server timed out waiting for the request. Client can retry.
409
Conflict
Request conflicts with current server state (e.g., duplicate resource, version mismatch).
410
Gone
Resource existed but has been permanently deleted. Unlike 404, this is intentional.
413
Payload Too Large
Request body exceeds server limits. Reduce payload size or use chunked uploads.
415
Unsupported Media Type
Server doesn't support the Content-Type (e.g., sending XML when JSON is required).
422
Unprocessable Entity
Request is well-formed but has semantic errors (e.g., validation failures).
429
Too Many Requests
Rate limit exceeded. Client should back off and retry after the Retry-After period.
5xx Server Error
500
Internal Server Error
Generic server error. Something went wrong on the server side.
501
Not Implemented
Server doesn't support the requested functionality.
502
Bad Gateway
Server acting as gateway received an invalid response from upstream server.
503
Service Unavailable
Server is temporarily unavailable (overloaded or under maintenance).
504
Gateway Timeout
Server acting as gateway did not receive a timely response from upstream.