418 I'm a teapot (RFC 2324, RFC 7168)

This is an educational reference page about HTTP 418 I'm a teapot. The page itself is served as 200 OK so it can be indexed as HTTP documentation.

This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee. This HTTP status is used as an Easter egg in some websites, such as Google.com's I'm a teapot easter egg.[53]

What it means

HTTP 418 I'm a teapot is a real registered status code from an April Fools RFC, but it is not intended for normal production errors.

Common causes

A site or API intentionally returns 418 as an easter egg.
A demo, test server, or joke endpoint implements the teapot response.
An application uses 418 incorrectly instead of a standard client or server error.

How to fix it

Use standard 4xx or 5xx codes for real application errors.
Keep 418 limited to jokes, demos, or compatibility with a known API contract.
Document any non-standard use so clients do not treat it as a generic failure.

Example response

HTTP/1.1 418 I'm a teapot
Content-Type: text/plain

Short and stout

Developer notes

418 is widely recognized by developers, but it should not replace precise status codes such as 400, 403, 404, or 500.

Questions

What does HTTP 418 mean?

HTTP 418 means I'm a teapot. It is a registered joke status code and is rarely appropriate for production API errors.

Is 418 I'm a teapot real?

Yes. HTTP 418 exists, but it came from an April Fools specification and is mostly used as a joke or easter egg.

Should APIs use HTTP 418 for real errors?

Usually no. Production APIs should use a status code that describes the actual client or server error.