Slack did the same thing which I really like -  <a href="https:&#x2F;&#x2F;api.slack.com&#x2F;methods" rel="nofollow">https:&#x2F;&#x2F;api.slack.com&#x2F;methods</a>. I was just thinking about JSON RPC style APIs vs &#x27;RESTful APIs.<p>REST APIs are nice because they follow the data model so closely but there are so many cases in which I am trying to overload something to bend the pattern to my needs. Then again, Stripe seems to have created a fantastic API that handles many complicated cases so maybe it just requires more upfront thought - <a href="https:&#x2F;&#x2F;stripe.com&#x2F;docs&#x2F;api" rel="nofollow">https:&#x2F;&#x2F;stripe.com&#x2F;docs&#x2F;api</a>.<p>I disagree that REST is a buzzword, though. I think that REST has become so popular because it&#x27;s a very effective way to construct an API.<p>afterthought: There are plenty of &quot;RESTful&quot; APIs that miss the mark on important concepts in the pattern. In this case, I would say - yes REST is worthy of the term buzzword.