HTTP Status Code Lookup
OK
The request succeeded.
Created
The request succeeded and a new resource was created.
No Content
The request succeeded but there's no content to return.
Moved Permanently
The resource has permanently moved to a new URL.
Found
The resource temporarily resides at a different URL.
Not Modified
The cached version is still valid; no need to re-fetch.
Bad Request
The server couldn't understand the request due to invalid syntax.
Unauthorized
Authentication is required and has failed or not been provided.
Forbidden
The server understood the request but refuses to authorize it.
Not Found
The server can't find the requested resource.
Method Not Allowed
The request method isn't supported for this resource.
Conflict
The request conflicts with the current state of the resource.
Gone
The resource is no longer available and won't be again.
Unprocessable Entity
The request was well-formed but contains semantic errors.
Too Many Requests
The user has sent too many requests in a given time.
Internal Server Error
The server encountered an unexpected condition.
Not Implemented
The server doesn't support the functionality required.
Bad Gateway
The server got an invalid response from an upstream server.
Service Unavailable
The server isn't ready to handle the request (overload/maintenance).
Gateway Timeout
The upstream server failed to respond in time.
Other tools in Developer Tools
About HTTP Status Code Lookup
Every HTTP response includes a three-digit status code indicating what happened to the request — and while a handful of codes (200, 404, 500) are famous enough that most developers know them by heart, the full standard includes dozens of codes covering much more specific situations, each with a precise, standardized meaning defined by HTTP specifications maintained by the IETF. Knowing exactly what a less common code means, rather than guessing from context, is often the fastest way to understand why an API call failed or behaved unexpectedly.
This reference organizes codes into their standard categories, each identifiable by its first digit: 2xx codes indicate success (the request was received, understood, and accepted); 3xx codes indicate redirection (further action is needed to complete the request, usually automatically by the browser or HTTP client); 4xx codes indicate a client error (something about the request itself was wrong — bad syntax, missing authentication, a resource that doesn't exist); and 5xx codes indicate a server error (the request was valid, but the server failed to fulfill it). Recognizing which category a code falls into, even before reading its specific meaning, immediately tells you whether to look at your request or suspect a problem on the server's end.
Beyond the famous few, this reference covers status codes that come up constantly in real API work but are less universally memorized: 429 (Too Many Requests, for rate limiting), 422 (Unprocessable Entity, for a request that's syntactically valid JSON but fails business logic validation), 304 (Not Modified, for HTTP caching), and 502/503/504 (the distinct flavors of "something's wrong upstream or the server's overloaded" that often get lumped together as "the API is down" without understanding which specific failure occurred).
Use the search box to jump straight to a code by number or by name — typing "404" or "not found" both find the same entry — which is faster than scanning a long static reference table when you already know roughly what you're looking for.
How it works
- Search by code or name. Type a status code number or part of its name to filter instantly.
- Read the meaning. Each entry shows its category color, official name, and a plain-language explanation.
Examples
Looking up 429
Input
429
Output
429 Too Many Requests — The user has sent too many requests in a given time.