HTTP Status Code Reference helps you test and debug APIs quickly and accurately, right in your browser. Whether you need to searchable reference of all http status codes with descriptions and use cases, this tool eliminatesintegration bugs, incorrect request formats, and protocol errors by giving you instant, reliable results. Every operation runs locally on your device — nothing is uploaded to any server, so your data stays completely private.
Key Features
Complete Reference
All HTTP status codes from 1xx to 5xx with RFC references.
Search & Filter
Filter by category (success, redirect, client error, server error).
Code Examples
Example responses and common scenarios for each status code.
Quick Copy
Copy status code descriptions and example responses.
Common Use Cases
- Quickly look up status codes while debugging API responses
- Learn proper status code usage when designing RESTful APIs
- Reference RFC documentation for custom API error responses
HTTP Status Code Reference
Searchable reference of all HTTP status codes with descriptions and use cases.
The server has received the request headers and the client should proceed to send the body.
The server is switching protocols as requested by the client.
The request succeeded. The meaning depends on the HTTP method used.
The request succeeded and a new resource was created.
The request succeeded but there is no content to return.
The URL has been permanently moved to a new location.
The URL has been temporarily moved to a new location.
The resource has not been modified since the last request.
The server cannot process the request due to a client error.
Authentication is required and has failed or not been provided.
The server understood the request but refuses to authorize it.
The requested resource could not be found.
The request method is not supported for the requested resource.
The server timed out waiting for the request.
The user has sent too many requests in a given amount of time.
A generic error message when the server encounters an unexpected condition.
The server received an invalid response from the upstream server.
The server is temporarily unable to handle the request.
The server did not receive a timely response from the upstream server.
Frequently Asked Questions
What is HTTP Status Code Reference?
HTTP Status Code Reference is an online API utility that searchable reference of all http status codes with descriptions and use cases. Features include Complete Reference, Search & Filter, Code Examples. Requests are made directly from your browser, with full visibility into headers, status codes, and response bodies.
Testing APIs typically involves dedicated desktop applications or command-line tools that can be cumbersome to set up. HTTP Status Code Reference provides a lightweight browser-based alternative that requires no installation or configuration. Each request is transparent — you see exactly what is sent and received — making it ideal for quick debugging, exploring new endpoints, or demonstrating API behavior to team members.
Frequently Asked Questions
What is the difference between 401 and 403?
401 Unauthorized means the client must authenticate. 403 Forbidden means the server understood the request but refuses to authorize it, even with authentication.
What does 502 Bad Gateway mean?
502 Bad Gateway means the server, acting as a gateway or proxy, received an invalid response from an upstream server it accessed to fulfill the request.
When should I use 201 vs 200?
Use 200 OK for successful requests that return data. Use 201 Created specifically when a POST request successfully creates a new resource.
Can I filter by status code category?
Yes. Use the category filters to show only 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), or 5xx (Server Error) codes.
How does the Complete Reference feature work?
The Complete Reference feature all http status codes from 1xx to 5xx with rfc references. It is designed to be intuitive and responsive, giving you immediate feedback as you interact with the tool. All processing happens locally in your browser.
What is the benefit of search & filter?
Search & Filter filter by category (success, redirect, client error, server error). This capability sets HTTP Status Code Reference apart from basic alternatives by providing more comprehensive functionality while maintaining the privacy and speed of local processing.
Is HTTP Status Code Reference really free to use?
Yes, HTTP Status Code Reference is completely free with no hidden charges, no sign-up requirements, and no usage limits. You can use it as often as you need, for any purpose — personal projects, commercial work, or educational use. There are no premium tiers or paid features.
Does HTTP Status Code Reference work on mobile devices?
Yes, it works on any device with a modern web browser — desktop, tablet, or phone. The interface is responsive and adapts to your screen size. Since all processing is done locally, you get the same performance regardless of your device.
What happens to my data when I use HTTP Status Code Reference?
Your data never leaves your device. Every operation is performed locally in your browser using JavaScript. No information is uploaded, stored, logged, or shared with any server. This privacy-first approach means you can work with sensitive data — passwords, API keys, personal information — without any risk of exposure.
Key Features
Complete Reference
All HTTP status codes from 1xx to 5xx with RFC references.
Search & Filter
Filter by category (success, redirect, client error, server error).
Code Examples
Example responses and common scenarios for each status code.
Quick Copy
Copy status code descriptions and example responses.
Common Use Cases
HTTP Status Code Reference is useful in a variety of scenarios across different workflows:
Quickly look up status codes while debugging API responses
Learn proper status code usage when designing RESTful APIs
Reference RFC documentation for custom API error responses
Tips & Best Practices
Use 201 for resource creation
Return 201 Created (not 200 OK) when a POST request successfully creates a new resource, and include the resource URL in the Location header.
Use 409 for conflicts
Return 409 Conflict when a request conflicts with the current state of the resource, such as duplicate entries or version conflicts.
Related Tools
Explore more api tools to enhance your workflow:
REST API Client
Send HTTP requests (GET, POST, PUT, DELETE) and inspect responses from your browser.
Request Builder
Build HTTP requests interactively and generate code snippets in multiple languages.
OpenAPI Validator
Validate OpenAPI 3.x and Swagger 2.0 specifications for correctness.
WebSocket Tester
Connect to WebSocket endpoints, send messages, and inspect frames.
curl to Fetch Converter
Convert curl commands to JavaScript fetch, Python requests, and more.
Mock API Generator
Generate mock API responses from JSON schemas for rapid development.
Related Guides & Articles
Deepen your knowledge with these api guides and tutorials:
Common Errors & Fixes
Learn how to fix common errors related to HTTP Status Code Reference:
400 Bad Request Error
Learn what 400 Bad Request means, common causes like malformed syntax or invalid request parameters, and how to fix them.
401 Unauthorized Error
Learn what a 401 Unauthorized error means, common causes, and how to fix authentication failures in your web applications.
403 Forbidden Error
Learn what 403 Forbidden means, how it differs from 401, and how to fix access denied errors in your applications.
404 Not Found Error
Learn what 404 Not Found means, common causes, and how to fix broken links and missing resources on your website or API.
408 Request Timeout Error
Learn what 408 Request Timeout means, why servers time out idle connections, and how to fix slow request issues.
413 Payload Too Large Error
Fix 413 Payload Too Large errors when uploading files or sending large request bodies.
422 Unprocessable Entity Error
Learn what 422 Unprocessable Entity means for API validation errors, how it differs from 400, and how to fix validation failures.
429 Too Many Requests Error
Learn what 429 Too Many Requests means, how rate limiting works, and how to handle or avoid hitting API rate limits.
500 Internal Server Error
Learn what 500 Internal Server Error means, common causes, and how to debug and fix server-side failures.
502 Bad Gateway Error
Learn what 502 Bad Gateway means, common causes like proxy or load balancer misconfiguration, and how to fix gateway errors.
503 Service Unavailable Error
Learn what 503 Service Unavailable means, how to fix maintenance mode and overload issues, and how to implement proper downtime handling.
504 Gateway Timeout Error
Fix 504 Gateway Timeout errors. Learn how proxies, load balancers, and CDNs time out waiting for upstream servers.
CORS Policy Blocked Request
Learn how to fix 'CORS policy: No Access-Control-Allow-Origin header' errors. Understand how CORS works and how to configure it correctly.
CORS Preflight Request Failed
Fix CORS preflight (OPTIONS) request failures. Learn how browsers check CORS permissions before making cross-origin requests.
npm ERR! ERESOLVE unable to resolve dependency tree
Fix npm ERESOLVE dependency resolution errors. Learn to use --legacy-peer-deps, update packages, and resolve conflicting peer dependency versions.
Port is Already Allocated (Docker)
Fix 'port is already allocated' Docker error when ports conflict between containers or host processes.