<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #rest</title>
    <link>/tags/rest/</link>
    <description>Recent bookmarks tagged #rest</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:45 +0000</lastBuildDate>
    <item>
      <title>Most RESTful APIs aren’t really RESTful | Florian Krämer</title>
      <link>https://florian-kraemer.net//software-architecture/2025/07/07/Most-RESTful-APIs-are-not-really-RESTful.html</link>
      <description>Fielding’s rules emphasize that a truly RESTful API should embrace hypermedia (HATEOAS) as the central mechanism for interaction, not just use HTTP as a transport. REST is protocol-independent at its core; HTTP is simply a convenient way of using it. Clients should discover and navigate resources dynamically through links and standardized relations embedded in representations — not rely on hardcoded URI structures, types, or external documentation.&#xD;&#xA;&#xD;&#xA;This makes REST systems loosely coupled, evolvable, and aligned with how the web itself operates: through representation, discovery, and transitions. REST isn’t about exposing your internal object model over HTTP — it’s about building distributed systems that behave like the web.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #rest #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 10 Jul 2025 02:54:13 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29456</guid>
      <category>apis</category>
      <category>rest</category>
      <category>webdev</category>
    </item>
    <item>
      <title>REST was NEVER about CRUD - Tyk API Gateway and API Management - REST was NEVER about CRUD</title>
      <link>https://tyk.io/blog/rest-never-crud/</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #api #dev #imported:pinboard #rest #web&lt;/p&gt;</description>
      <pubDate>Sat, 21 Jul 2018 15:47:01 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:31285</guid>
      <category>api</category>
      <category>dev</category>
      <category>imported:pinboard</category>
      <category>rest</category>
      <category>web</category>
    </item>
    <item>
      <title>REST was NEVER about CRUD - Tyk API Gateway and API Management - REST was NEVER about CRUD</title>
      <link>https://tyk.io/blog/rest-never-crud</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #api #dev #rest #web&lt;/p&gt;</description>
      <pubDate>Sat, 21 Jul 2018 15:47:01 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:27788</guid>
      <category>api</category>
      <category>dev</category>
      <category>rest</category>
      <category>web</category>
    </item>
    <item>
      <title>RFC 6570 - URI Template</title>
      <link>http://tools.ietf.org/html/rfc6570</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #api #http #imported:pinboard #rest #template #uri&lt;/p&gt;</description>
      <pubDate>Tue, 28 Apr 2015 00:52:16 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:25650</guid>
      <category>api</category>
      <category>http</category>
      <category>imported:pinboard</category>
      <category>rest</category>
      <category>template</category>
      <category>uri</category>
    </item>
    <item>
      <title>draft-nottingham-json-home-02 - Home Documents for HTTP APIs</title>
      <link>http://tools.ietf.org/html/draft-nottingham-json-home-02</link>
      <description>This document proposes a &#34;home document&#34; format for non-browser HTTP&#xD;&#xA;   clients.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #imported:pinboard #json #rest #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 06 Mar 2015 15:59:04 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:25528</guid>
      <category>imported:pinboard</category>
      <category>json</category>
      <category>rest</category>
      <category>webdev</category>
    </item>
    <item>
      <title>What is the RESTed NARWHL? | The RESTed NARWHL</title>
      <link>http://www.narwhl.com/</link>
      <description>Where REST is an architectural style for APIs, NARWHL is a framework intended to provide a roadmap for those needing to implement an API using current best practices but flexible enough to grow into the future.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #gluecon #imported:pinboard #narwhl #rest #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 22 May 2014 16:03:48 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:31878</guid>
      <category>apis</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>narwhl</category>
      <category>rest</category>
      <category>webdev</category>
    </item>
    <item>
      <title>What is the RESTed NARWHL? | The RESTed NARWHL</title>
      <link>http://www.narwhl.com</link>
      <description>Where REST is an architectural style for APIs, NARWHL is a framework intended to provide a roadmap for those needing to implement an API using current best practices but flexible enough to grow into the future.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #gluecon #narwhl #rest #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 22 May 2014 16:03:48 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:24866</guid>
      <category>apis</category>
      <category>gluecon</category>
      <category>narwhl</category>
      <category>rest</category>
      <category>webdev</category>
    </item>
    <item>
      <title>WebhookInbox</title>
      <link>http://webhookinbox.com/</link>
      <description>WebhookInbox receives HTTP requests and&#xD;&#xA;captures the data for later inspection.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #debugging #http #imported:pinboard #rest #tools #webdev&lt;/p&gt;</description>
      <pubDate>Sun, 14 Jul 2013 23:51:35 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32242</guid>
      <category>apis</category>
      <category>debugging</category>
      <category>http</category>
      <category>imported:pinboard</category>
      <category>rest</category>
      <category>tools</category>
      <category>webdev</category>
    </item>
    <item>
      <title>WebhookInbox</title>
      <link>http://webhookinbox.com</link>
      <description>WebhookInbox receives HTTP requests and&#xD;&#xA;captures the data for later inspection.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #debugging #http #rest #tools #webdev&lt;/p&gt;</description>
      <pubDate>Sun, 14 Jul 2013 23:51:35 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23917</guid>
      <category>apis</category>
      <category>debugging</category>
      <category>http</category>
      <category>rest</category>
      <category>tools</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Elastic Path™ Cortex Studio</title>
      <link>http://cortexgraph.jitsu.com/#help</link>
      <description>Nifty REST API browser&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #elasticpath #gluecon #imported:pinboard #rest&lt;/p&gt;</description>
      <pubDate>Thu, 23 May 2013 18:00:08 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23694</guid>
      <category>apis</category>
      <category>elasticpath</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>rest</category>
    </item>
    <item>
      <title>Secure Your REST API... The Right Way | Stormpath</title>
      <link>http://www.stormpath.com/blog/secure-your-rest-api-right-way</link>
      <description>We already showed you how to build a Beautiful REST+JSON API, but how do you secure your API?  At Stormpath we spent 18 months researching best practices, implementing them in the Stormpath API, and figuring out what works. Here’s our playbook on how to secure a REST API.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #auth #gluecon #imported:pinboard #rest #security #services&lt;/p&gt;</description>
      <pubDate>Thu, 23 May 2013 00:21:25 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23678</guid>
      <category>apis</category>
      <category>auth</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>rest</category>
      <category>security</category>
      <category>services</category>
    </item>
    <item>
      <title>Designing REST + JSON APIs | Stormpath</title>
      <link>http://www.stormpath.com/blog/designing-rest-json-apis</link>
      <description>Les recently gave a talk on &#34;Designing a Beautiful REST + JSON API&#34; at the San Francisco Java Users Group, which covers 18 months of his research into API design.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #gluecon #imported:pinboard #json #rest&lt;/p&gt;</description>
      <pubDate>Wed, 22 May 2013 22:48:17 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23665</guid>
      <category>apis</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>json</category>
      <category>rest</category>
    </item>
    <item>
      <title>Combining HTML Hypermedia APIs and Adaptive Web Design – Jayway</title>
      <link>http://www.jayway.com/2012/08/01/combining-html-hypermedia-apis-and-adaptive-web-design/</link>
      <description>HTML is the lowest common denominator in a world where the number of devices are steadily growing. In such a world, our API should be hypermedia driven and we should consider choosing HTML as the media type for our APIs. If we choose this, we can enhance the API with CSS and JavaScript, making the API human-friendly as well. Further, we can use Adaptive Web Design to make the best possible experience for all types of browsers and devices.  This kind of solution has some risks and technical issues related to it though. And it is not a silver bullet.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #html #hypermedia #imported:pinboard #rest #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 13 Dec 2012 23:12:27 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32620</guid>
      <category>html</category>
      <category>hypermedia</category>
      <category>imported:pinboard</category>
      <category>rest</category>
      <category>webdev</category>
    </item>
    <item>
      <title>REST is OVER! - Literate Programming</title>
      <link>http://blog.steveklabnik.com/posts/2012-02-23-rest-is-over</link>
      <description>Yep. Sorry to have to inform you. REST is totally over. The cool kids are moving on. We&#39;re building &#34;Hypermedia APIs&#34; now. Such is life.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #hypermedia #imported:pinboard #rest #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 02 Mar 2012 05:34:44 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:21038</guid>
      <category>apis</category>
      <category>hypermedia</category>
      <category>imported:pinboard</category>
      <category>rest</category>
      <category>webdev</category>
    </item>
    <item>
      <title>A Hypermedia API Reading List - Literate Programming</title>
      <link>http://blog.steveklabnik.com/posts/2012-02-27-hypermedia-api-reading-list</link>
      <description>Originally, this post was titled &#34;A RESTful Reading List,&#34; but please note that REST is over. Hypermedia API is the new nomenclature.&#xD;&#xA;&#xD;&#xA;I&#39;ve been doing an intense amount of research on Hypermedia APIs over the last few months, and while I didn&#39;t save every resource I found, I&#39;ve made a list here of the most important.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #hypermedia #imported:pinboard #rest #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 02 Mar 2012 05:34:34 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:21037</guid>
      <category>apis</category>
      <category>hypermedia</category>
      <category>imported:pinboard</category>
      <category>rest</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
