HTTP Status Code Reference
Search common HTTP response codes, learn what they mean, and get practical first checks for API troubleshooting.
| Code | Meaning | Description | QA troubleshooting tip |
|---|
Reference: MDN HTTP response status codes · IANA registry. A response's exact meaning and behavior can depend on the endpoint and application contract.
How to troubleshoot HTTP status codes
Interpret a status code together with the endpoint contract, response body, headers, and server logs. The code alone rarely identifies the root cause.
Quick QA troubleshooting guide
- 400 Bad Request: inspect payload syntax, required fields, parameter names, and content type.
- 401 Unauthorized: check whether credentials are present, valid, and correctly formatted.
- 403 Forbidden: verify the user's permissions and resource access rules.
- 404 Not Found: confirm the route, resource identifier, environment, and HTTP method.
- 409 Conflict: check duplicate operations, state conflicts, or version constraints.
- 429 Too Many Requests: review rate limits and any Retry-After guidance.
- 500 Internal Server Error: correlate the request with server logs without exposing sensitive details.
- 502 / 503 / 504: investigate upstream availability, service health, and gateway timeouts.
Frequently asked questions
Is every 4xx response a bug?
No. A 4xx response may be the correct result for invalid input, missing authentication, or denied access. Compare it with the documented contract.
Is every 5xx response caused by my request?
No. 5xx responses indicate server-side or gateway failures, but request patterns, dependencies, and service configuration can contribute. Check logs and reproduce safely.
Can I expect every API to use the same error body?
No. Error response bodies and headers vary by API. Validate them against that API's documented contract.