HTTP Status Codes Cheat Sheet

HTTP response status codes

What this cheat sheet is for

This http status codes reference helps you complete common developer tasks quickly and avoid repeated trial-and-error when working under deadlines.

When you need a reliable command or pattern during debugging and incident response.
When you are implementing a feature and want a known-good syntax example immediately.
When onboarding teammates and documenting repeatable workflows for daily use.
When reviewing pull requests and verifying that command usage follows best practices.

200 OK
201 Created
204 No Content

301 Moved Permanently
302 Found
304 Not Modified

400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
429 Too Many Requests

500 Internal Server Error
502 Bad Gateway
503 Service Unavailable

People often copy a command or pattern without adapting placeholders, which can break production workflows unexpectedly.
It is easy to forget environment-specific differences, so always verify behavior in your shell, runtime, or API gateway before shipping.
Many errors come from skipping small validation steps, so test with realistic sample input before relying on the result.

Last updated: February 2026