HTTP status code 418 — I'm a teapot
Quick answer
Status code 418 (I'm a teapot): Joke status from HTCPCP — server refuses to brew coffee. Rarely used in real APIs; sometimes appears in demos or Easter eggs.
Rarely used in real APIs; sometimes appears in demos or Easter eggs.
418 is not a serious production signal. If you see it in the wild, check whether a middleware or mock is being playful.
Common causes
- A framework Easter egg route (many web frameworks ship one for fun)
- A mock/test server intentionally returning it
How to fix it
Nothing to fix in production — if a real endpoint returns 418, ask whoever built it why.
Related: 415422413410409408500502
Frequently asked questions
What is status code 418?
418 I'm a teapot: Joke status from HTCPCP — server refuses to brew coffee. Rarely used in real APIs; sometimes appears in demos or Easter eggs.
When should I expect HTTP 418?
418 is not a serious production signal. If you see it in the wild, check whether a middleware or mock is being playful.
What usually causes HTTP 418?
A framework Easter egg route (many web frameworks ship one for fun); A mock/test server intentionally returning it.
How do I fix HTTP 418?
Nothing to fix in production — if a real endpoint returns 418, ask whoever built it why.
Where can I see all status codes?
Open the HTTP status codes hub on TryDevSnip for the full reference list.
Does TryDevSnip log my API traffic?
No. These pages are static reference. TryDevSnip does not proxy or inspect your HTTP calls.