<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hateoas on cloudmato.com</title><link>https://cloudmato.com/tags/hateoas/</link><description>Recent content in Hateoas on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Sun, 05 Jul 2026 19:47:46 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/hateoas/index.xml" rel="self" type="application/rss+xml"/><item><title>HATEOAS: What It Is and Why Almost No One Uses It</title><link>https://cloudmato.com/posts/hateoas-rest-api-why-nobody-implements-it/</link><pubDate>Sun, 05 Jul 2026 19:47:46 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/hateoas-rest-api-why-nobody-implements-it/</guid><description>&lt;p&gt;Everyone is building &amp;ldquo;REST APIs&amp;rdquo; nowadays. You have got endpoints, you return JSON, you use &lt;code&gt;GET&lt;/code&gt; and &lt;code&gt;POST&lt;/code&gt; and &lt;code&gt;DELETE&lt;/code&gt;, you send back &lt;code&gt;404&lt;/code&gt; when something is missing. Congratulations, you have a REST API. Right?&lt;/p&gt;
&lt;p&gt;Well, according to the person who literally coined the term REST, probably not. And the piece you are missing is a scary-looking acronym called &lt;strong&gt;HATEOAS&lt;/strong&gt; — the one part of REST that almost nobody implements and most people can&amp;rsquo;t even spell. I have been writing APIs for more than 8 years and honestly, for the longest time I treated HATEOAS as academic trivia. So let me untangle it: what it is, why the industry collectively ignores it, and the more interesting question — when you actually earn the right to call your thing a REST API.&lt;/p&gt;</description></item></channel></rss>