HTTP Status Code Explorer

Comprehensive reference for HTTP status codes with examples and use cases

Overview

The HTTP Status Code Explorer provides a comprehensive, searchable reference for all HTTP status codes from 1xx to 5xx. Search by code number or name, filter by category, and learn what each code means, when to use it, and how to handle it properly in your applications.

Tips

  1. Search by Code or Name: Quickly find status codes by typing the number (like “404”) or searching for keywords (like “not found” or “redirect”) to locate the exact code you need.

  2. Filter by Category: Use the category filters (1xx, 2xx, 3xx, 4xx, 5xx) to narrow down results. For example, filter by 4xx to see all client error codes when debugging user-facing errors.

  3. Understand 401 vs 403: Use 401 when authentication is missing or invalid (user needs to log in), and 403 when the user is authenticated but lacks permission (access denied even with valid credentials).

  4. Use 201 for Creation: Always return 201 Created (not 200 OK) when creating new resources, and include a Location header pointing to the new resource’s URI for proper REST API design.

  5. Include Helpful Error Details: Don’t just return status codes alone - include descriptive error messages in the response body to help developers debug issues. For example, return validation details with 400 Bad Request responses.