HTTP Status Code Reference
Continue
Initial part of the request has been received; client should continue.
Switching Protocols
Server is switching to a different protocol as requested.
Processing
Server has received the request but has not yet completed it.
Early Hints
Server sends preliminary headers before the final response.
OK
The request has succeeded.
Created
Request succeeded and a new resource was created.
Accepted
Request accepted for processing but not yet completed.
Non-Authoritative Information
Response metadata is from a local or third-party copy.
No Content
Request succeeded but there is no content to return.
Reset Content
Server asks client to reset the document view.
Partial Content
Server is delivering part of the resource due to a range header.
Multi-Status
Response contains multiple status codes for multiple operations.
Already Reported
Members of a DAV binding have already been enumerated.
IM Used
Server has fulfilled a GET request with instance-manipulations.
Multiple Choices
Multiple options for the resource; client may choose one.
Moved Permanently
Resource has been permanently moved to a new URL.
Found
Resource temporarily resides at a different URL.
See Other
Response can be found at a different URI using GET.
Not Modified
Resource has not been modified since the last request.
Use Proxy
Requested resource must be accessed through a specified proxy.
Temporary Redirect
Resource temporarily at a different URL; method must not change.
Permanent Redirect
Resource permanently moved; method must not change.
Bad Request
Server cannot process the request due to client error.
Unauthorized
Authentication is required and has failed or not been provided.
Payment Required
Reserved for future use; sometimes used for payment-related errors.
Forbidden
Server understood the request but refuses to authorize it.
Not Found
The requested resource could not be found on the server.
Method Not Allowed
HTTP method is not supported for the requested resource.
Not Acceptable
Server cannot produce a response matching the Accept headers.
Proxy Authentication Required
Client must authenticate with a proxy server.
Request Timeout
Server timed out waiting for the client's request.
Conflict
Request conflicts with the current state of the server.
Gone
Resource is permanently gone and will not return.
Length Required
Server requires a Content-Length header in the request.
Precondition Failed
One or more conditions in the request headers were not met.
Content Too Large
Request entity is larger than the server is willing to process.
URI Too Long
The request URI is longer than the server is willing to interpret.
Unsupported Media Type
Server does not support the media type of the request body.
Range Not Satisfiable
The requested range cannot be fulfilled by the server.
Expectation Failed
Server cannot meet the Expect header requirements.
I'm a Teapot
Server refuses to brew coffee because it is a teapot.
Misdirected Request
Request was directed at a server unable to produce a response.
Unprocessable Content
Request is well-formed but contains semantic errors.
Locked
The resource is currently locked.
Failed Dependency
Request failed because it depended on another failed request.
Too Early
Server unwilling to process a request that might be replayed.
Upgrade Required
Client should switch to a different protocol.
Precondition Required
Server requires the request to be conditional.
Too Many Requests
Client has sent too many requests in a given time period.
Request Header Fields Too Large
Server refuses the request because headers are too large.
Unavailable For Legal Reasons
Resource unavailable due to legal demands.
Internal Server Error
Server encountered an unexpected condition preventing the request.
Not Implemented
Server does not support the requested functionality.
Bad Gateway
Server received an invalid response from an upstream server.
Service Unavailable
Server is temporarily unable to handle the request.
Gateway Timeout
Server did not receive a timely response from upstream.
HTTP Version Not Supported
Server does not support the HTTP version used in the request.
Variant Also Negotiates
Server has an internal configuration error in content negotiation.
Insufficient Storage
Server cannot store the representation needed to complete the request.
Loop Detected
Server detected an infinite loop while processing the request.
Not Extended
Further extensions to the request are required for the server to fulfill it.
Network Authentication Required
Client needs to authenticate to gain network access.
Category Reference
Request received, continuing process
Request successfully received, understood, and accepted
Further action needed to complete the request
Request contains bad syntax or cannot be fulfilled
Server failed to fulfill a valid request
What This Tool Does
HTTP Status Code Reference is built for deterministic developer and agent workflows.
Interactive searchable reference for all HTTP status codes with descriptions and use cases.
Use How to Use for execution steps and FAQ for constraints, policies, and edge cases.
Last updated:
This tool is provided as-is for convenience. Output should be verified before use in any production or critical context.
Agent Invocation
Best Path For Builders
Browser workflow
Runs instantly in the browser with private local processing and copy/export-ready output.
Browser Workflow
This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.
/http-status-codes/
For automation planning, fetch the canonical contract at /api/tool/http-status-codes.json.
How to Use HTTP Status Code Reference
- 1
Search by status code
Enter a code (e.g., 404, 500) to see its meaning, description, and common use cases. Quick reference for understanding API errors.
- 2
Search by description
Search for keywords like 'not found', 'server error', or 'success'. The tool returns matching status codes, letting you pick the right one for your response.
- 3
Browse by category
Group by status code families: 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client error), 5xx (server error). Understand which category applies to your scenario.
- 4
Use in API error handling
Reference this tool when implementing error responses. Return 400 for bad requests, 401 for auth failures, 403 for permission denied, 404 for missing resources, 500 for server errors. Use correct codes for proper client error handling.