This playground answers with 61 different HTTP status codes — not as documentation, but as live endpoints you can call right now. Each page explains what the code means, why you would provoke it deliberately, and which endpoints produce it.
Success
200 OK — The request succeeded and the response carries the representation you asked for. For a GET this is the body; for a PUT or POST it is the result of the operation.
201 Created — A new resource exists as a result of this request. A well-behaved API also sends a Location header pointing at it, and usually the created representation as the body.
202 Accepted — The request was accepted but has not been carried out yet. The work happens asynchronously, and the response tells you where to look for the result.
203 Non-Authoritative Information — The request succeeded, but the body was modified by a transforming proxy between you and the origin server — it is not exactly what the origin sent.
204 No Content — The request succeeded and there is deliberately no body. Most commonly the answer to a successful DELETE.
205 Reset Content — The request succeeded and the client should reset the view that sent it — clear the form, so the user can enter another. There is never a body.
206 Partial Content — The response carries only the byte range you asked for with a Range header, described by Content-Range. This is how resumable downloads and media seeking work.
207 Multi-Status — One response carrying several independent outcomes, for a request that operated on more than one resource. Each element has its own status.
Redirection
300 Multiple Choices — The resource has several representations and the server is asking the client to pick one, usually listing them in the body and optionally suggesting one in Location.
301 Moved Permanently — The resource has a new URL, given in the Location header, and clients should use it from now on.
302 Found — The resource is temporarily at a different URL. Unlike a 301, the original URL stays authoritative and should still be used for future requests.
303 See Other — The answer is somewhere else, at the URL in Location, and the client should fetch it with GET — whatever method the original request used.
304 Not Modified — The answer to a conditional GET whose If-None-Match matched the current ETag: your cached copy is still valid, so no body is sent.
307 Temporary Redirect — The resource is temporarily at another URL; repeat the same request — same method, same body — there, and keep using the original URL afterwards.
308 Permanent Redirect — The resource has moved permanently to the URL in Location; repeat the same request there, method and body unchanged, and use the new URL from now on.
Client error
400 Bad Request — The server could not understand the request — malformed JSON, a missing required field, or a parameter of the wrong type.
401 Unauthorized — Authentication is missing or invalid. Despite the name, this is about identity, not permission — the server does not know who you are.
402 Payment Required — Reserved in the original spec and now used in practice for quota, billing and insufficient-funds conditions.
403 Forbidden — The server knows who you are and is refusing anyway. Authentication succeeded; authorization did not.
404 Not Found — There is no resource at this URL. The server will not say whether there ever was one.
405 Method Not Allowed — The URL exists but not with this method. The response must include an Allow header listing what is permitted.
406 Not Acceptable — The server cannot produce a representation matching your Accept header.
407 Proxy Authentication Required — A proxy between you and the server needs credentials before it will forward the request. It names the scheme it wants in Proxy-Authenticate.
408 Request Timeout — The server gave up waiting for the client to finish sending the request, and has closed (or will close) the connection.
409 Conflict — The request is valid but clashes with the current state — a duplicate, a seat already taken, a state transition that is not allowed from here.
410 Gone — The resource existed and has been permanently removed. Unlike a 404, the server is stating that it will not come back.
411 Length Required — The server refuses a request with a body but no Content-Length header, because it will not accept a chunked or unbounded body.
412 Precondition Failed — A condition in the request headers was not met — almost always an If-Match ETag that no longer reflects the current state of the resource.
413 Content Too Large — The request body exceeds what the server will accept. Still widely known by its old reason phrase, Payload Too Large.
414 URI Too Long — The request URI is longer than the server is willing to interpret, usually because too much data went into the query string.
415 Unsupported Media Type — The body is in a format the endpoint does not accept — usually a Content-Type mismatch.
416 Range Not Satisfiable — The Range header asks for bytes that do not exist — typically an offset past the end of the resource.
417 Expectation Failed — The server cannot meet the expectation in the request's Expect header — in practice, Expect: 100-continue.
418 I'm a Teapot — HTTP 418 is a reserved status code. Its “I’m a teapot” meaning comes from RFC 2324, a 1998 April Fools’ specification about brewing coffee. The current HTTP specification, RFC 9110, lists it as unused.
421 Misdirected Request — The request reached a server that is not able to answer for the host it asked about, typically because an HTTP/2 connection was reused for the wrong origin.
422 Unprocessable Content — The syntax is fine and the server understood the request, but the content is semantically wrong — a valid date in the past where a future one is required, a transfer that would overdraw an account.
423 Locked — The resource is locked, and this request would need the lock it does not hold.
424 Failed Dependency — This operation failed because another operation it depended on failed first.
425 Too Early — The server will not process a request sent in TLS early data (0-RTT), because it could be replayed by an attacker.
426 Upgrade Required — The server refuses to serve this request over the current protocol and names the one to switch to in the Upgrade header.
428 Precondition Required — The server requires this request to be conditional — to carry If-Match or similar — so that a write cannot overwrite a change it has not seen.
429 Too Many Requests — You are being rate limited. The response should carry Retry-After, and usually X-RateLimit-Limit, -Remaining and -Reset.
431 Request Header Fields Too Large — The request's headers are too large — all together, or one of them on its own — for the server to process.
451 Unavailable For Legal Reasons — The server will not serve this resource for legal reasons — a court order, a government block or a takedown that applies to the requester.
499 Client Closed Request — Non-standard, from nginx: the client closed the connection before the server sent a response. nginx writes it to the access log; no client ever receives it over the wire.
Server error
500 Internal Server Error — The server failed and cannot say anything more useful. Nothing about the request needs to be wrong.
501 Not Implemented — The server does not support the functionality required — usually the HTTP method itself — for any resource.
502 Bad Gateway — A gateway or proxy got an invalid response from the server behind it — a crash, a closed connection, garbage instead of HTTP.
503 Service Unavailable — The server is temporarily unable to handle the request — overloaded, or down for maintenance. Often accompanied by Retry-After.
504 Gateway Timeout — An upstream server did not respond in time. The failure is in the chain behind the endpoint, not at the endpoint itself.
507 Insufficient Storage — The server cannot store the representation needed to complete the request — it has run out of space.
508 Loop Detected — The server stopped processing because it detected an infinite loop — typically a resource that, directly or indirectly, includes itself.
511 Network Authentication Required — The client has to authenticate to gain network access — the response comes from a captive portal, not from the server you asked for.
520 Web Server Returned an Unknown Error — Non-standard, from Cloudflare: the origin answered with something Cloudflare could not interpret — an empty, malformed or unexpected response, or a reset connection.
521 Web Server Is Down — Non-standard, from Cloudflare: the origin server refused the connection — it is down, or a firewall is blocking the CDN's addresses.
522 Connection Timed Out — Non-standard, from Cloudflare: the TCP connection to the origin timed out before it was established.
523 Origin Is Unreachable — Non-standard, from Cloudflare: the origin could not be reached at all — typically a DNS record pointing at the wrong address or a routing problem.
524 A Timeout Occurred — Non-standard, from Cloudflare: the connection to the origin succeeded, but no HTTP response arrived before the proxy timeout (125 seconds by default — Cloudflare's Proxy Read Timeout).
525 SSL Handshake Failed — Non-standard, from Cloudflare: the TLS handshake between the CDN and the origin failed — no common cipher, no certificate, or a misconfigured TLS listener.
526 Invalid SSL Certificate — Non-standard, from Cloudflare: the origin presented a certificate the CDN would not accept under strict validation — expired, self-signed or for the wrong host.