HTTP Status Codes Cheat Sheet
Quickly look up, understand, and resolve HTTP response codes from 1xx to 5xx with troubleshooting tips.
Continue
Server has received the request headers and client should proceed to send body.
Switching Protocols
Requester has asked the server to switch protocols (e.g. WebSocket handshake).
OK
Standard response for successful HTTP requests.
Created
The request succeeded and a new resource was successfully created.
Accepted
The request has been accepted for processing, but processing is not yet complete.
No Content
Server successfully processed the request and is not returning any content.
Partial Content
Server is delivering only part of the resource due to a Range header sent by client.
Moved Permanently
The target resource has been assigned a new permanent URI.
Found (Temporary Redirect)
The target resource resides temporarily under a different URI.
Not Modified
Resource has not been modified since the version specified in If-Modified-Since header.
Temporary Redirect
Same as 302, but guarantees the HTTP request method (e.g. POST) is not changed.
Permanent Redirect
Same as 301, but guarantees the HTTP method will not change.
Bad Request
The server cannot or will not process request due to an apparent client error.
Unauthorized
Authentication is required and has failed or has not yet been provided.
Forbidden
The request was valid, but the server is refusing action (insufficient permissions).
Not Found
The requested resource could not be found on the server.
Method Not Allowed
A request method is not supported for the requested resource.
Request Timeout
The server timed out waiting for the client to send the request.
Conflict
Request could not be processed because of conflict in current state of resource.
Unprocessable Entity
Request was well-formed but was unable to be followed due to semantic errors.
Too Many Requests
The user has sent too many requests in a given amount of time (Rate Limiting).
Internal Server Error
A generic error message, given when an unexpected condition was encountered.
Not Implemented
The server either does not recognize the request method, or lacks ability to fulfill.
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response.
Service Unavailable
The server cannot handle request due to temporary overloading or maintenance.
Gateway Timeout
The server acting as a gateway or proxy did not receive a timely response.
RFC Specifications
Accurate definitions based on IETF RFC 7231, RFC 7540, and modern HTTP semantics for REST and GraphQL APIs.
Actionable Fixes
Each status code includes concrete troubleshooting instructions for frontend developers and DevOps engineers.
Instant Filter
Search by status number, phrase, or keyword to immediately diagnose API responses and network errors.