Posted on 09-06-2012
I’m exploring the future of web APIs, and have come to what I feel is what of the most fascinating areas of evolution in the usage of web APIs. An approach that is very developer centric, which is something you don't always see in the current API service landscape.
There are two companies working hard on developing new libraries for popular programming languages that abstract away much of the authentication and other complexities developers face when using APIs.
Temboo and Webshell are two pioneers that are taking API development to a new level. Temboo is building libraries in Java, PHP, Python, or Ruby and Webshell is building libraries in JS, PHP, Ruby as well as providing a command line interface for programming against APIs.
This isn’t just programming directly against a single API. These are libraries that allow you to make calls against APIs using sometimes as little as 2 or 3 lines of code, opening new possibilities of efficiently programming against not just one API, but fluently across multiple APIs.
In addition to simplifying calls made against APIs, both platforms work to abstract away the complexities of API authentication, one of the biggest pain points for developers.
Platforms like Temboo and Webshell absorb the complexity, inconsistencies and difficult aspects of programming using APIs, providing libraries that developers can use in their native programming languages--making developers lives easier.
It’s tough to classify what Temboo and Webshell are doing. I don’t have a term or phrase to describe them--one that does them justice. Everything I say sounds like everything you are already doing with individual APIs. But this is more. Temboo and Webshell are defining new ways of speaking using APIs, allowing us to more efficiently speak using the vast amount of valuable resources being exposed via web APIs today.
Temboo and Webshell both have their own approach to solving this problem, which I will dive into separately, in future posts. Right now I just want to identify what they are doing to move forward the API landscape.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- 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
- APIs That Do One Thing And Do It Well Like ZipLocate