Fork me on GitHub


Hypermedia, also known as HATEOAS or Hypermedia the Engine of Application State, as defined by Wikipedia is "a constraint of the REST application architecture that distinguishes it from most other network application architectures. The principle is that a client interacts with a network application entirely through hypermedia provided dynamically by application servers. A REST client needs no prior knowledge about how to interact with any particular application or server beyond a generic understanding of hypermedia."

Hypermedia discussion have been going on for some time now, but in the last two year we've seen Hypermedia go from what is seen as academic dicussions to proven implmentations in the wild, showing the benefits of other REST implementations.

While there are still a limited amount of tooling out there to support Hypermedia API implementations, and there are no companies that exclusively target the area, the increase in the number of Hypermedia APIs warrants taking a closer look a the space. As I do with other areas, as I work to understand different approaches I want to help tell stories about hypermedia APIs that the mainstream can relate with.

As part of this reserch I'm aggregating companies, and individuals who are doing interesting things in the space, as well as the tools, services, and other stories around their work. The more hypermedia is discussed in the space, the more you'll see this research grow.


We Dont Need Many Hypermedia Formats Fresh Blurbs By Irakli Nadareishvili

(Posted on )

Views expressed on this blog are mine alone and do not necessarily reflect the views of my employer.In addition, commenters are responsible for their comments.Earlier today, I had a very interesting Twitter exchange with Darrel Miller.That exchange inspired me to share some of my thoughts about media types, in the context of Hypermedia Architecture and APIs.Before we ask that question, what we really should be asking is: why do we even need media types? more.


(Posted on )

Mike Admundsen visited the Lonely Planet offices recently and spent all day discussing the current state of API development, and thoughts on what the future holds – for those brave enough to take the risk.One thing that I walked away from the day-long event with was the thought, “Ok, so we’ve mostly been doing this for a decade and we’ve kinda painted ourselves into a corner, but there’s a few people who are trying to do it the right way.Why can’t we, today, start churning out hypermedia APIs and clients that can easily consume them?” Well, the answer is: It’ more.

Translating The World Of Hypermedia APIs For The Normals

(Posted on )

I’m giving my hypermedia API research a little love today, and as part of this I was reviewing examples of hypermedia in the wild like with the Elastic Path Cortex API. Elastic Path was the first company to introduce me to the possibilities around hypermedia way back in 2011, so I enjoy checking in regularly to see what they are up to with their APIs. As of January 2014 I’ve committed more time to doing research on hypermedia APIs, as well as work to tell stories about how hypermedia is being applied by companies, in a way that anyone more.