Your HTTP-based API is not RESTful

Many developers mock RPC-interfaces, SOAP and the like. Instead they go on to build “RESTful” HTTP interfaces using descriptive URLs and HTTP verbs to standardize actions. They document their URLs and the actions that can be taken on each of them as their API. Finally they build applications consuming these interfaces based on the API spec. The above is *not* REST. It’s RPC all over again.

What everyone forgets is the design principle of “hypermedia as the engine of application state”. This talk will attempt to shed some light on this principle and share a few ideas for working with it in practice.

Smarter Tech Decisions Using APIs

Smarter Tech Decisions Using APIs

API blog

High impact blog posts and eBooks on API business models, and tech advice

API conferences

Connect with market leading platform creators at our events

API community

Join a helpful community of API practitioners

API Insights Straight to Your Inbox!

Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High impact blog posts on API business models and tech advice.

Join Our Thriving Community

Become a part of our global community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.