It&#x27;s really not, I&#x27;m sorry.<p>State is carried by the client, the client traverses links to find out what it can do, the responses are described by a published content type, and the content type defines the semantics of the protocol.<p>It&#x27;s not hard, but people like to pretend that it is. Nothing says you can&#x27;t stick to GET and POST, nothing requires weird headers.<p>&quot;ReST in Practice&quot; is a great introduction for engineers.