A complete, searchable reference for all standard HTTP status codes. Click any code to see detailed descriptions, common causes, example scenarios, and how to fix or handle each one.
Showing 32 of 32 status codes
The server has received the request headers and the client should proceed to send the request body.
The server is switching protocols as requested by the client via the Upgrade header.
The server has received and is processing the request, but no response is available yet (WebDAV).
Used to return some response headers before the final HTTP message, allowing the browser to preload resources.
The request has succeeded. The meaning of the success depends on the HTTP method used.
The request has been fulfilled and a new resource has been created as a result.
The request has been accepted for processing, but the processing has not been completed yet.
The server has successfully processed the request but is not returning any content in the response body.
The server is delivering only part of the resource due to a Range header sent by the client.
The resource has been permanently moved to a new URL. All future requests should use the new URL.
The resource has been temporarily moved to a different URL. The client should continue using the original URL.
The response to the request can be found at a different URL using a GET request.
The resource has not been modified since the last request. The client can use its cached version.
The resource is temporarily at a different URL. The request method and body must not be changed when following the redirect.
The resource has permanently moved to a new URL. The request method and body must not be changed when following the redirect.
The server cannot process the request due to malformed syntax, invalid parameters, or missing required fields.
The request lacks valid authentication credentials. The client must authenticate to access the resource.
The server understood the request but refuses to authorize it. Authentication will not help.
The server cannot find the requested resource. The URL may be incorrect or the resource may have been deleted.
The HTTP method used is not supported for the requested resource.
The server timed out waiting for the client to send the complete request.
The request conflicts with the current state of the resource on the server.
The resource is no longer available and has been permanently removed. Unlike 404, this is intentional and permanent.
The request payload is larger than the server is willing or able to process.
The server refuses the request because the payload format is not supported.
The request is well-formed but contains semantic errors that prevent processing.
The client has sent too many requests in a given time period (rate limiting).
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
The server, acting as a gateway or proxy, received an invalid response from the upstream server.
The server is temporarily unable to handle the request, typically due to maintenance or overload.
The server, acting as a gateway or proxy, did not receive a timely response from the upstream server.
All standard HTTP status codes from 1xx to 5xx in one place
Search by code number or description text instantly
Filter by category: Informational, Success, Redirection, Client Error, Server Error
Detailed explanations with common causes for each code
Real-world example scenarios to understand each status code
Actionable fix and handling guidance for every code
Quickly look up the correct status code to return from your REST API endpoints for different scenarios.
Understand what went wrong when you encounter an unfamiliar status code in browser DevTools or server logs.
Study the full range of HTTP status codes with clear explanations and practical examples.
Reference accurate status code descriptions when writing API documentation or troubleshooting guides.
Love our free tools? Discover our AI-powered products that help businesses automate customer communication.
Automate phone calls with AI. Handle appointments, inquiries, and support 24/7 in 40+ languages.
Build WhatsApp chatbots without coding. Automate support and boost sales with 98% open rates.
Add an intelligent chatbot to your website. Convert visitors, answer questions, and capture leads 24/7.
Translate and dub videos in 100+ languages with natural AI voices. Reach global audiences in minutes.
Turn every call into insights with AI transcription, sentiment analysis, and quality scoring for support and sales teams.
Visual deal pipeline with drag-and-drop kanban, Gmail integration, and contact management. Close more deals faster.
Connect customers and staff on a masked number so personal numbers stay private. Click-to-call masking with a simple REST API.
Local, toll-free, and virtual numbers across India from Rs 349/month. Call forwarding, IVR, and free number porting included.
Elastic SIP trunking at 50 paisa/min. Connect any PBX or AI voice agent to the Indian PSTN. No contracts, self-serve setup.
Recurring revenue for Shopify. Pause/skip, build-a-box, prepaid plans, and a customer portal with UPI Autopay & Razorpay.