Best Practices for Designing a Pragmatic RESTful API | Vinay Sahni. Your data model has started to stabilize and you're in a position to create a public API for your web app. You realize it's hard to make significant changes to your API once it's released and want to get as much right as possible up front. Now, the internet has no shortage on opinions on API design. But, since there's no one widely adopted standard that works in all cases, you're left with a bunch of choices: What formats should you accept? How should you authenticate? Should your API be versioned? In designing an API for Enchant (a Zendesk Alternative), I've tried to come up with pragmatic answers to these questions. ... or just skip to the bottom and signup for updates Latest from the Enchant blog How to make your app lovable A decent app helps you get the job done. ... and those apps, the ones that make things feel effortless, are the ones we love the most.
But what makes an app feel effortless? Key requirements for the API Use RESTful URLs and actions But what can I make a resource? RESTful API in WCF get called more than one time, but client called it once only!! What is wrong? Your answer is here!! Learn REST: A Tutorial. Roy.gbiv.com/talks/200709_fielding_rest.pdf. How I Explained REST to My Wife.