Developer Reference
HTTP Status Codes Cheatsheet
A complete list of HTTP status codes, their meanings, and troubleshooting tips. Perfect for debugging API responses and server errors.
HTTP status codes are the language of the web. They tell you (and your browser) whether a request was successful, if there was an error, or if authentication is required. This definitive list covers 1xx, 2xx, 3xx, 4xx, and 5xx response codes.
Success
The request succeeded.
OK
The request succeeded, and a new resource was created as a result.
Created
The server successfully processed the request and is not returning any content.
No Content
Redirection
The URL of the requested resource has been changed permanently.
Moved Permanently
The URI of requested resource has been changed temporarily.
Found
Indicates that the resource has not been modified since the version specified by the request headers.
Not Modified
Request should be repeated with another URI; future requests can use original.
Temporary Redirect
Request and all future requests should be repeated using another URI.
Permanent Redirect
Client Error
The server cannot or will not process the request due to an apparent client error.
Bad Request
Authentication is required and has failed or has not been yet provided.
Unauthorized
The request contained valid data and was understood by the server, but the server is refusing action.
Forbidden
The requested resource could not be found but may be available in the future.
Not Found
A request method is not supported for the requested resource.
Method Not Allowed
The user has sent too many requests in a given amount of time.
Too Many Requests
Target resource does not have current content acceptable according to Accept headers.
Not Acceptable
Request could not be processed because of conflict in the request (e.g. edit conflict).
Conflict
Server understands content type and syntax but cannot process the contained instructions.
Unprocessable Entity
The user requests an illegal resource (e.g. censored by government).
Unavailable For Legal Reasons
Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Internal Server Error
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Bad Gateway
The server is currently unavailable (because it is overloaded or down for maintenance).
Service Unavailable
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
Gateway Timeout
Fun
The server requires a teapot to brew coffee (April Fools Joke / Hyper Text Coffee Pot Control Protocol).
I'm a teapot
Mastering HTTP status codes is essential for backend and frontend development. Use this cheatsheet to quickly identify why an API call failed or how to handle specific server responses.