Word Counter
Count words, characters, and analyze text.
API Debugging Utility
HTTP Status Explorer
Search HTTP status codes, inspect production-style request/response examples, copy payloads, and understand when each status should be used.
Search status code
63 codes matched
200 OK
2xx
Request succeeded.
Standard success code for many request types.
Example request
GET /v1/resource HTTP/1.1
Host: api.example.devExample response
HTTP/1.1 200 OK
Content-Type: application/json
{"status":"ok","code":200}Copy-ready custom response template
Edit this for mocks, tests, or API docs snippets.
Developer explanation: choosing the right status code
Use status codes to describe protocol-level outcomes, not internal implementation details. Pick the most specific code that matches behavior: 400 for malformed requests, 422 for validation errors, 401 for missing/invalid auth, 403 for permission failures, and 409 for state conflicts. Correct code usage improves debugging, client retry behavior, observability dashboards, and SEO signals for public web routes.
Common API mistakes
- Returning 200 for all responses and hiding failure in JSON body fields.
- Using 500 for user input errors that should be 4xx.
- Mixing 401 and 403 incorrectly.
- Returning 404 for authorization failures where 403 is clearer for internal APIs.
FAQs
What is the difference between 400 and 422?
Use 400 Bad Request when the server cannot parse the request (malformed JSON, invalid syntax). Use 422 Unprocessable Content when the payload is syntactically valid but fails business validation rules such as invalid field formats or domain constraints.
When should I use 401 vs 403?
Use 401 Unauthorized when authentication is missing or invalid. Use 403 Forbidden when authentication is valid but the user is not allowed to perform the action.
Is 200 OK appropriate for every API response?
No. Returning 200 for failures hides protocol meaning and makes debugging harder. Prefer accurate 4xx/5xx codes so clients, logs, and monitoring systems can react correctly.
Why is 304 Not Modified important?
304 responses let clients reuse cached resources, which reduces bandwidth and improves performance. They are typically used with ETag or Last-Modified conditional requests.
Does this tool include copyable response templates?
Yes. You can copy built-in example responses for each status code and also edit/copy a custom response template for docs, mocks, and API tests.
Is Free HTTP Status Explorer - Status Codes, Examples, and API Guidance free to use?
Free HTTP Status Explorer - Status Codes, Examples, and API Guidance is completely free and runs in your browser.
Does Free HTTP Status Explorer - Status Codes, Examples, and API Guidance send my data to a server?
No. Free HTTP Status Explorer - Status Codes, Examples, and API Guidance processes input directly in your browser.
Do I need to create an account to use Free HTTP Status Explorer - Status Codes, Examples, and API Guidance?
No account is required to use Free HTTP Status Explorer - Status Codes, Examples, and API Guidance.
Privacy-first by design
Tool inputs are processed in your browser. Review the Privacy Policy and Terms for full details.
Related Tools
All ToolsOpen Tool →
Regex Tester
Test your regular expressions instantly.
Regex Library
Use ready regex patterns with explanations and built-in testing.
URL Query Parser
Inspect query parameters as key/value pairs.