Slack did the same thing which I really like - https://api.slack.com/methods https://api.slack.com/methods. I was just thinking about JSON RPC style APIs vs 'R

Slack did the same thing which I really like - https://api.slack.com/methods https://api.slack.com/methods. I was just thinking about JSON RPC style APIs vs 'RESTful APIs. 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 - https://stripe.com/docs/api https://stripe.com/docs/api. I disagree that REST is a buzzword, though. I think that REST has become so popular because it's a very effective way to construct an API. afterthought: There are plenty of "RESTful" 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.