<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rest on cloudmato.com</title><link>https://cloudmato.com/tags/rest/</link><description>Recent content in Rest on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Mon, 08 Jun 2026 00:03:37 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/rest/index.xml" rel="self" type="application/rss+xml"/><item><title>Can You Still Call an API RESTful Without Every Rule?</title><link>https://cloudmato.com/posts/can-i-call-my-api-restful/</link><pubDate>Mon, 08 Jun 2026 00:03:37 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/can-i-call-my-api-restful/</guid><description>&lt;p&gt;Everyone slaps &amp;ldquo;RESTful&amp;rdquo; on their API. Open any docs page, scroll the marketing copy, and there it is — &amp;ldquo;our clean, RESTful API.&amp;rdquo; But here&amp;rsquo;s the uncomfortable bit: by the strict definition, almost none of them actually are. So the question you&amp;rsquo;re really asking is whether the word still means anything if you break some of the rules. Honestly, that&amp;rsquo;s where it gets tricky.&lt;/p&gt;
&lt;p&gt;Short answer first, because I hate articles that bury it: &lt;strong&gt;yes, you can still call it RESTful in everyday conversation, but no, it isn&amp;rsquo;t a REST API by Roy Fielding&amp;rsquo;s original definition unless it&amp;rsquo;s hypertext-driven.&lt;/strong&gt; Both of those things are true at the same time, and the gap between them is the whole story.&lt;/p&gt;</description></item></channel></rss>