:mastodon: Mike Amundsen<p>How to (and how not to) design REST APIs</p><p><a href="https://github.com/stickfigure/blog/wiki/How-to-(and-how-not-to)-design-REST-APIs" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/stickfigure/blog/wi</span><span class="invisible">ki/How-to-(and-how-not-to)-design-REST-APIs</span></a></p><p>"In my career, I have consumed hundreds of REST APIs and produced dozens. Since I often see the same mistakes repeated in API design, I thought it might be nice to write down a set of best practices. And poke fun at a couple widely-used APIs." -- <a href="https://mastodon.social/tags/JeffSchnitzer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JeffSchnitzer</span></a></p><p><a href="https://mastodon.social/tags/api360" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>api360</span></a> <a href="https://mastodon.social/tags/apiDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>apiDesign</span></a> <a href="https://mastodon.social/tags/apiGuidance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>apiGuidance</span></a></p>