Home/Cheat Sheets/HTTP Status Codes

HTTP Status Codes Cheat Sheet

Every HTTP status code you need to know, organized by class. A quick visual reference for developers, sysadmins, and anyone working with web APIs.

HTTP Status Codes — Quick Referencejustprotocols.com1xx InformationalCodeNameDescription100ContinueClient should continue request101Switching ProtocolsServer switching to requested protocol103Early HintsPreload resources before final response2xx SuccessCodeNameDescription200OKRequest succeeded201CreatedResource created successfully204No ContentSuccess, no body returned206Partial ContentRange request fulfilled207Multi-StatusWebDAV batch response3xx RedirectionCodeNameDescription301Moved PermanentlyResource permanently at new URL302FoundTemporary redirect (commonly used)303See OtherRedirect with GET304Not ModifiedCached version is current307Temporary RedirectRedirect, keep method308Permanent RedirectPermanent redirect, keep method4xx Client ErrorCodeNameDescription400Bad RequestMalformed request syntax401UnauthorizedAuthentication required403ForbiddenServer refuses to authorize404Not FoundResource does not exist405Method Not AllowedHTTP method not supported408Request TimeoutClient took too long409ConflictRequest conflicts with current state413Payload Too LargeRequest body exceeds limit415Unsupported Media TypeContent type not supported422Unprocessable EntityValid syntax but semantic errors429Too Many RequestsRate limit exceeded5xx Server ErrorCodeNameDescription500Internal Server ErrorUnexpected server failure501Not ImplementedServer doesn't support functionality502Bad GatewayInvalid response from upstream503Service UnavailableServer overloaded or in maintenance504Gateway TimeoutUpstream server timed out
HTTP status codes grouped by class — 1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, 5xx Server Error

Status Code Classes

1xxInformational — The server has received the request headers and the client should proceed. These are provisional responses before the final answer.
2xxSuccess — The request was received, understood, and accepted. The action requested by the client was completed successfully.
3xxRedirection — The client must take additional action to complete the request, usually following a different URL provided in the response.
4xxClient Error — The request contains bad syntax or cannot be fulfilled. The problem is on the client side and the request should be corrected before retrying.
5xxServer Error — The server failed to fulfill a valid request. The problem is on the server side and the client may retry later.

Most Common in Practice

These are the status codes developers encounter most often when building and consuming APIs:

200 Standard success response
201 Resource created (POST success)
301 Permanent URL redirect (SEO)
302 Temporary redirect (login flows)
400 Invalid request data
401 Missing or invalid credentials
403 Insufficient permissions
404 Resource not found
500 Unhandled server exception

Learn More About HTTP

Understand the protocol behind these status codes, including request methods, headers, and how HTTPS secures the connection.