Skip to main content
TellaDev
Cheatsheets HTTP Status Codes

26 entries

HTTP Status Codes

HTTP response status codes for informational, success, redirect, client error, and server error responses

26 commands

100 Continue
Server has received request headers; client should proceed to send the body
Expect: 100-continue header sent
101 Switching Protocols
Server agrees to switch protocols (e.g., HTTP to WebSocket)
Upgrade: websocket
200 OK
The request succeeded; response body contains the result
GET /api/users → 200 OK
201 Created
The request succeeded and a new resource was created (common after POST)
POST /api/users → 201 Created
202 Accepted
Request accepted for processing, but processing is not complete
POST /jobs/export → 202 Accepted
204 No Content
Request succeeded but there is no response body (common for DELETE)
DELETE /api/users/42 → 204
206 Partial Content
Server is delivering only part of the resource due to a range request
Range: bytes=0-1023 → 206
301 Moved Permanently
Resource has been permanently moved to a new URL; update your links
http→https redirect (301)
302 Found
Resource temporarily located at a different URL; keep using the original
GET /old-page → 302 → /new-page
304 Not Modified
Resource has not changed since the last request; use the cached version
If-None-Match: "etag" → 304
307 Temporary Redirect
Temporary redirect that preserves the HTTP method of the original request
POST /v1/pay → 307 → /v2/pay
308 Permanent Redirect
Permanent redirect that preserves the HTTP method of the original request
/api → 308 → /api/v2
400 Bad Request
The server cannot process the request due to malformed syntax or invalid data
{ "error": "missing 'email' field" }
401 Unauthorized
Authentication is required and has failed or not been provided
Missing or expired Bearer token
403 Forbidden
Server understood the request but refuses to authorize it (authenticated but no permission)
Valid token, but role != admin
404 Not Found
The requested resource could not be found on the server
GET /api/users/999 → 404
405 Method Not Allowed
The HTTP method used is not allowed for the requested resource
POST /api/health → 405
409 Conflict
Request conflicts with the current state of the resource (e.g., duplicate entry)
PUT /users (duplicate email) → 409
410 Gone
Resource is permanently deleted and will not be available again
GET /api/v1/legacy → 410 Gone
422 Unprocessable Entity
Request is well-formed but has semantic errors (common in REST API validation)
{ "errors": { "age": "must be > 0" } }
429 Too Many Requests
Client has sent too many requests in a given time (rate limiting)
Retry-After: 60
500 Internal Server Error
Generic server error when no more specific message is available
Unhandled exception in handler
501 Not Implemented
Server does not support the functionality required to fulfill the request
PATCH method not supported
502 Bad Gateway
Server acting as a gateway received an invalid response from an upstream server
Nginx upstream timeout
503 Service Unavailable
Server is temporarily unable to handle requests (overloaded or maintenance)
Deploy in progress, retry later
504 Gateway Timeout
Server acting as a gateway did not receive a timely response from an upstream server
Upstream did not respond in 30s