HTTP Status Codes List
Quickly copy a complete, ordered reference of official HTTP status codes and reason phrases.
HTTP status codes(64 registered status codes)
Based on the IANA HTTP Status Code Registry. Includes registered special cases like temporary, unused, and obsoleted entries; excludes unassigned ranges.
How to use this list
Use HTTP codes in 3 quick steps
Takes ~5 seconds- 1Choose your output format
Pick text for docs, JSON for code, or HTML for select menus.
- 2Copy or download
Use one-click copy or download the output for later use.
- 3Paste into your workflow
Use in API references, automated tests, or error-handling UIs.
Common use cases
- Backend and frontend developers documenting API responses
- QA engineers building response-code test matrices
- Platform teams standardizing monitoring and alert labels
Examples
Success response label.
200
200 OK
Client error response label.
429
429 Too Many Requests
Server error response label.
503
503 Service Unavailable
Reliable HTTP response-code reference
This list helps teams keep HTTP status code names consistent across specs, implementation, and operations tooling.
Need a complete HTTP status codes list for API development, testing, or observability? This page provides the IANA-registered status code entries in copy-ready text, JSON, and HTML formats. Use text output for runbooks and documentation, JSON for app constants and automated checks, or HTML <option> tags for internal tooling interfaces. The list is ordered numerically and includes official labels for informational, success, redirection, client error, and server error responses. It also marks registered edge entries such as temporary, unused, and obsoleted status codes so you can handle protocol details accurately in production workflows.
Includes all currently IANA-registered HTTP status code entries in numeric order.
- 1xx to 5xx coverage
- Official reason phrases
- Deterministic ordering
Switch between text, JSON, and HTML outputs with one click.
- Plain text list
- JSON array
- HTML <option> tags
Useful for API docs, tests, dashboards, logs, and validation rules.
- QA fixtures
- Monitoring labels
- Developer docs
HTTP status code best practices
Use consistent status code semantics across API design and runtime behavior.
- Align each endpoint with a documented set of expected status codes.
- Distinguish retryable vs non-retryable errors in client logic.
- Log both numeric code and reason phrase for faster debugging.
Frequently asked questions
Does this include unofficial or vendor-specific status codes?>
Are unassigned status code ranges included?>
Why are some entries labeled temporary, unused, or obsoleted?>
Related Developer lists
Copy common application/* MIME types in text, JSON, or HTML format for API content negotiation, downloads, and file validation.
Copy common audio MIME types in text, JSON, or HTML format for uploads, playback support checks, and processing pipelines.
Copy a practical common MIME types list in text, JSON, or HTML format for uploads, APIs, validation, and content handling.
Copy all HTTP 2xx success codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows, ready to paste.
Copy all HTTP 3xx redirect codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows, ready to paste.
Copy all HTTP 4xx client error codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows.
Copy all HTTP 5xx server error codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows.
Copy a clean http request methods list (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE, CONNECT) in text, JSON, or HTML for API docs and tooling.
Copy common image MIME types in text, JSON, or HTML format for upload validation, image processing, and media tooling.
Copy common video MIME types in text, JSON, or HTML format for upload policies, streaming workflows, and player support checks.