HTTP Status Codes
Complete reference of HTTP status codes with descriptions and examples
Search Status Codes
All Codes
Informational
Success
Redirection
Client Error
Server Error
Informational
Request received, continuing process
Continue
The server has received the request headers, and the client should proceed to send the request body.
Common Usage
Used with Expect: 100-continue header for large uploads
Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
Common Usage
Upgrading from HTTP to WebSocket protocol
Processing
The server has received and is processing the request, but no response is available yet.
Common Usage
WebDAV request processing
Early Hints
Used to return some response headers before final HTTP message.
Common Usage
Preloading resources while server prepares response
Success
Request successfully received, understood, and accepted
OK
The request has succeeded. The meaning of success depends on the HTTP method used.
Common Usage
GET request returns the requested resource
Created
The request has been fulfilled and has resulted in one or more new resources being created.
Common Usage
POST request successfully creates a new user
Accepted
The request has been accepted for processing, but the processing has not been completed.
Common Usage
Asynchronous job queued for background processing
Non-Authoritative Information
The request was successful but the enclosed payload has been modified by a transforming proxy.
Common Usage
Response from a caching proxy with modified headers
No Content
The server successfully processed the request, but is not returning any content.
Common Usage
DELETE request successfully removes a resource
Reset Content
The server successfully processed the request, and is instructing the client to reset the document view.
Common Usage
Form submission that requires the form to be cleared
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
Common Usage
Video streaming with Range requests
Redirection
Further action needs to be taken to complete the request
Multiple Choices
The request has more than one possible response. The user or user agent should choose one of them.
Common Usage
Resource available in multiple formats (JSON, XML)
Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
Common Usage
Old domain redirects to new domain permanently
Found
The URI of requested resource has been changed temporarily. Further changes in the URI might be made in the future.
Common Usage
Temporary redirect during maintenance
See Other
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
Common Usage
POST request redirects to GET after form submission
Not Modified
The resource has not been modified since the version specified by the request headers.
Common Usage
Browser cache validation with If-Modified-Since
Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI with the same method.
Common Usage
Temporary redirect preserving request method
Permanent Redirect
The resource is now permanently located at another URI, specified by the Location header.
Common Usage
Permanent redirect preserving request method
Client Error
Request contains bad syntax or cannot be fulfilled
Bad Request
The server cannot process the request due to client error (e.g., malformed request syntax).
Common Usage
Invalid JSON in request body
Unauthorized
The client must authenticate itself to get the requested response.
Common Usage
Missing or invalid authentication token
Payment Required
Reserved for future use. Originally intended for digital payment systems.
Common Usage
Experimental use in payment APIs
Forbidden
The client does not have access rights to the content. Unlike 401, the client identity is known.
Common Usage
User authenticated but lacks permission to access resource
Not Found
The server cannot find the requested resource. This is one of the most common error codes.
Common Usage
Requesting a non-existent API endpoint or page
Method Not Allowed
The request method is known by the server but is not supported by the target resource.
Common Usage
Sending POST to an endpoint that only accepts GET
Not Acceptable
The server cannot produce a response matching the list of acceptable values in the request headers.
Common Usage
Client requests XML but server only provides JSON
Request Timeout
The server would like to shut down this unused connection. Sent on an idle connection.
Common Usage
Client takes too long to send complete request
Conflict
The request conflicts with the current state of the server.
Common Usage
Attempting to create a resource that already exists
Gone
The requested content has been permanently deleted from server, with no forwarding address.
Common Usage
Resource was deleted and will not be available again
Payload Too Large
Request entity is larger than limits defined by server.
Common Usage
File upload exceeds maximum allowed size
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
Common Usage
URL with excessive query parameters
Unsupported Media Type
The media format of the requested data is not supported by the server.
Common Usage
Sending image/png when server expects application/json
I'm a teapot
The server refuses to brew coffee because it is, permanently, a teapot. (April Fools' joke from 1998)
Common Usage
HTCPCP protocol (Hyper Text Coffee Pot Control Protocol)
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Common Usage
Validation errors in form data
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
Common Usage
API rate limit exceeded
Server Error
Server failed to fulfill a valid request
Internal Server Error
The server has encountered a situation it does not know how to handle.
Common Usage
Unhandled exception in server code
Not Implemented
The request method is not supported by the server and cannot be handled.
Common Usage
Server does not support CONNECT method
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
Common Usage
Nginx cannot reach upstream application server
Service Unavailable
The server is not ready to handle the request. Common causes are server maintenance or overload.
Common Usage
Server temporarily down for maintenance
Gateway Timeout
The server is acting as a gateway and cannot get a response in time from the upstream server.
Common Usage
Upstream service takes too long to respond
HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
Common Usage
Using HTTP/3 on server that only supports HTTP/1.1
About HTTP Status Codes
HTTP status codes are standardized three-digit codes returned by web servers to indicate the result of a client's request. This comprehensive reference guide covers all standard HTTP status codes organized by category: informational (1xx), success (2xx), redirection (3xx), client error (4xx), and server error (5xx).
Each status code includes its official name, a detailed description of when it's used, and real-world examples to help you understand their practical applications. Whether you're debugging API responses, building RESTful services, or learning web development, this searchable reference makes it easy to find and understand any HTTP status code.
Common codes like 200 (OK), 404 (Not Found), and 500 (Internal Server Error) are joined by less common but equally important codes like 418 (I'm a teapot), 429 (Too Many Requests), and 503 (Service Unavailable). Use the search bar to quickly find specific codes or browse by category to explore different response types.
Need webhook testing?
HooksDash provides instant webhook endpoints, request inspection, and local forwarding. Perfect for testing the requests you build here.