HTTP Status Code Lookup
Enter an HTTP status code to get its name, description, common causes, and how to fix it. Covers all standard codes (1xx through 5xx) plus unofficial Cloudflare and Nginx codes.
Enter a status code between 100 and 599
returns
- data.name
- Official name, like Too Many Requests.
- data.description
- Plain explanation of what the code means.
- data.common_causes
- Usual reasons you'd see this code.
- data.how_to_fix
- Practical steps to resolve it.
- data.category
- Class name like Client Error, with 4xx in category_code.
- data.is_error
- True for 4xx and 5xx codes.
Run it from your code
A temporary key takes one request and lasts seven days at 20 calls a day. Register and it becomes 75 a day, still free.
$ curl -s "https://apixies.io/api/v1/http-status?code=404" \ -H "X-API-Key: $APIXIES_KEY" | jq '.data.name' "Too Many Requests"
questions
What HTTP status codes does this cover?
All standard codes from RFC 7231 and related RFCs (100-511), plus commonly used unofficial codes from Cloudflare (520-527), Nginx (444, 499), and Twitter (420).
What is the difference between 401 and 403?
401 means the request lacks valid authentication credentials. 403 means the server understood the request but refuses to authorize it, even with valid credentials. Think of 401 as "who are you?" and 403 as "you can't do that."
Why do I keep getting 429 errors?
429 means you're sending too many requests. Implement exponential backoff, check the Retry-After header, and consider batching requests or requesting higher rate limits from the API provider.