Web
HTTP Status Codes
Search common response codes and connect their short descriptions to the request, headers, and application behavior.
About this tool
When to use it
Search common response codes and connect their short descriptions to the request, headers, and application behavior.
How to use it
Search the code observed in your network log and read its meaning. Inspect the request method, response headers, and server log before deciding whether to retry or change the client.
Guide updated . Examples checked against this implementation.
Worked examples
Accepted is not completed
Input
Search: 202Expected output
202 Accepted — Request accepted for asynchronous processing.Acceptance does not establish that background work finished. The API should define how the client observes eventual completion or failure.
Errors and unsupported input
Retrying every failed request immediatelyInspect the status and protocol guidance first. A malformed request needs correction, while a rate-limit response may require waiting and checking retry instructions.
Continue this workflow
- MIME Types: Check request media types when investigating a 415 response.
Format references
Questions
Frequently asked questions
Does 200 prove the application result is correct?
It indicates successful HTTP handling as defined by the endpoint. Validate the response body and application semantics separately.