API Design
HTTP Status Code Reference
Search HTTP status codes by number or scenario. Covers 2xx, 3xx, 4xx, and 5xx codes with correct usage, common misuse patterns, and caching implications.
No data is transmitted — everything runs locallyTool
About this tool
HTTP Status Code Reference
The HTTP Status Code Reference covers all standard status codes with correct usage scenarios, common misuse patterns, caching implications, and rarely-used but semantically correct codes.
• Look up the correct status code for an async operation that started but isn't done
• Find which redirect code preserves the HTTP method (307 vs 302)
• Check whether a 403 or 404 is correct when hiding resource existence
• Reference the correct status code for rate limiting with retry-after
Next step
Rate Limit Header Generator — Generate correct HTTP rate limit response headers from your limits and remaining quota.
Open Rate Limit Header Generator →
FAQ
What does this tool tell you?
The HTTP Status Code Reference covers all standard status codes with correct usage scenarios, common misuse patterns, caching implications, and rarely-used but semantically correct codes.
What affects the result most?
2xx: 200 OK, 201 Created, 204 No Content, 206 Partial Content, 207 Multi-Status (WebDAV/batch). 3xx: 301 Moved Permanently (cache forever), 302 Found (don't cache), 307 Temporary Redirect (method preserved), 308 Permanent Redirect (method preserved). 4xx: 400 Bad Request, 401 Unauthorized (no auth), 403 Forbidden (auth insufficient), 404 Not Found, 409 Conflict, 422 Unprocessable Entity, 429 Too Many Requests.
How should I use the result?
Use this tool to orient quickly to the concepts, field names, or values you are about to look up in a full specification or vendor documentation. It summarizes the common cases; the authoritative source remains whichever standard or vendor doc defines the values themselves.
Related tools