HTTP Status Codes
Every HTTP response status code with its name and meaning — 200, 301, 404, 500 and more — grouped 1xx to 5xx. Search by number or name.
HTTP status codes are grouped by their first digit: 1xx informational, 2xx success, 3xx redirection, 4xx client errors and 5xx server errors. So 200 means OK, 301 a permanent redirect, 404 not found and 500 an internal server error. Search above by number (like 404) or by name (like "gateway"). To try requests and see the codes your API returns, use the API Tester.
Frequently Asked Questions
What are the five classes of HTTP status codes?
HTTP status codes are grouped by their first digit into five classes. 1xx are informational — the request was received and processing continues. 2xx mean success, such as 200 OK. 3xx are redirection, such as 301 Moved Permanently. 4xx are client errors — the request was faulty — such as 404 Not Found or 403 Forbidden. 5xx are server errors — the server failed to fulfil a valid request — such as 500 Internal Server Error.
What is the difference between 301 and 302?
301 and 302 are both redirects. 301 Moved Permanently tells clients and search engines the resource has moved for good, so they update bookmarks and pass link equity to the new URL. 302 Found is temporary — the move is short-lived and the original URL should still be used. Use 301 for permanent moves so search engines transfer ranking; use 302 or 307 for temporary ones such as maintenance.
What does a 404 versus a 500 error mean?
404 Not Found is a client error: the server works fine but there is nothing at the URL, often a broken link or typo. 500 Internal Server Error is a server error: the request was valid but something went wrong on the server, such as an unhandled exception. 4xx points at the request; 5xx points at the server, which is why 500s usually need a look at server logs.
What is a 429 Too Many Requests error?
429 Too Many Requests is a client error meaning you've sent more requests in a given time than the server allows, usually because of rate limiting. Many servers include a Retry-After header telling the client how long to wait before trying again. It is common on public APIs, and the fix is to slow down or batch requests rather than treat it as a bug.