HTTP Status Codes

What is HTTP Status Codes?

HTTP Status Code Reference provides a searchable database of all standard HTTP status codes (1xx through 5xx) defined in RFC 7231 and related RFCs, with detailed explanations, common causes, and proper usage guidance for each code. It covers informational (100-199), success (200-299), redirection (300-399), client error (400-499), and server error (500-599) ranges, including less common codes like 418 I'm a Teapot, 429 Too Many Requests, and 451 Unavailable For Legal Reasons. The tool includes example API response bodies for each code.

API developers choosing response codes, backend engineers implementing error handling, and technical writers documenting API behavior. The tool runs entirely in your browser — your data never leaves your device.

How to Use HTTP Status Codes

1. Browse status codes by category (1xx, 2xx, 3xx, 4xx, 5xx) or search by number or keyword
2. Click any code to see its full description, when to use it, and common causes
3. View example response bodies showing the standard error format for each code
4. Copy the description for use in API documentation or error handling code comments

Common Use Cases

• Looking up the correct status code to return from an API endpoint for a specific scenario
• Debugging unexpected HTTP responses by understanding what a particular status code means
• Learning the difference between similar codes like 401 vs 403, or 301 vs 302 vs 308
• Building API documentation with accurate status code descriptions and example responses

Pro Tips

• Use 201 Created (not 200 OK) when a POST request successfully creates a new resource — include a Location header pointing to the new resource's URL for proper RESTful behavior
• 401 Unauthorized actually means unauthenticated (no valid credentials), while 403 Forbidden means authenticated but not authorized (insufficient permissions) — the naming is confusing but the distinction matters for client-side error handling
• 429 Too Many Requests should include a Retry-After header telling the client when to try again — without it, clients retry immediately and make the overload worse

Why Use This Tool?

• Privacy-first: All processing happens locally in your browser. No data is transmitted to any server.
• No installation required: Works in any modern browser on desktop or mobile.
• Completely free: No account, no credit card, no usage caps.
• Fast and reliable: Powered by modern Web APIs for near-instant results.

Related Concepts

Learn more about related topics: RFC 7231, REST API, Error handling, HTTP protocol.

Frequently Asked Questions