Posted on 11-20-2013
With the growing number of hypermedia API deployments, hypermedia haters© are going to lose a major argument, that hypermedia is just an academic exercise and will never work in the wild. ;-)
The latest hypermedia API I was told about in the wild(thanks @johnmusser), is from Amazon Web Services with the recent AppStream API--"a flexible, low-latency service that lets you stream resource intensive applications and games from the cloud".
The AWS AppStream API is an API that uses Hypertext Application Language (HAL), a consistent and easy way to hyperlink between API resources, created by Mike Kelly(@mikekelly85) of Stateless.co. When HAL is used, with each API request, you get a wealth of links that allow you to programmatically explore the functionality of an API.
For example, you can explore the JSON returned in each response from the application API endpoint, about a specific app you are streaming including using the services, you will find links to determine application status, show information on current session and many more.
Normally with APIs, developers have to explore each API endpoint, and read through documentation to understand the different actions that can be taken against an API. With HAL, API owners can craft links that provide meaningful actions that can be discovered and implemented by developers along the way, teaching them about what is possible with each API call.
Hypermedia goes a long way in extending business rules to developers, not just directing them to what next steps may be taken at each API request, but really save them a lot of homework on how your API business model works, and how to best build an application around an API.
There are other hypermedia APIs in the wild, including the very important Public Media Platform (PMP), but the numbers are still low. I will keep finding quality hypermedia solutions in the wild and sharing them with you as I find.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems