HTTP 201 Created vs 418 I'm a Teapot
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://statuscodefyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://statuscodefyi.com/entity//Add a dynamic SVG badge to your README or docs.
[](https://statuscodefyi.com/entity//)Use the native HTML custom element.
HTTP 201 (Created) is a 2xx Success response, while 418 (I'm a Teapot) is a 4xx Client Error response. 201 indicates that the request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity. In contrast, 418 means that any attempt to brew coffee with a teapot should result in this error. An April Fools' joke from 1998 that became a beloved part of HTTP culture.
Description
The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
When You See It
After successfully creating a new user, post, order, or other resource via a REST API.
How to Fix
No fix needed. Check the Location header for the URL of the new resource.
Description
Any attempt to brew coffee with a teapot should result in this error. An April Fools' joke from 1998 that became a beloved part of HTTP culture.
When You See It
As an Easter egg on some websites, or when a server humorously refuses a request.
How to Fix
Use a coffee pot instead of a teapot. Or just enjoy the joke.
Key Differences
201 is a 2xx Success response, while 418 is a 4xx Client Error response.
HTTP 201: The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
HTTP 418: Any attempt to brew coffee with a teapot should result in this error. An April Fools' joke from 1998 that became a beloved part of HTTP culture.
You encounter 201 when after successfully creating a new user, post, order, or other resource via a REST API.
You encounter 418 when as an Easter egg on some websites, or when a server humorously refuses a request.
When to Use Which
For 201 (Created): No fix needed. Check the Location header for the URL of the new resource. For 418 (I'm a Teapot): Use a coffee pot instead of a teapot. Or just enjoy the joke.