Posted on 12-19-2012
I’m working hard to understand the emerging patterns of of how APIs used, work through the details, and grasp the differences in competing approaches--in hopes of identifying what is next when it comes to web APIs.
One trend I’m tracking on is the emergence of API scripting platforms. This is a difficult are to track on, because we script against APIs all the time, right? This is different. Scripting platforms are providing platforms and libraries to support easily scripting against multiple APIs.
To help me understand this new approach to using APIs I’m studying three separate approaches:
- Webshell - Authentication, integration and scripting platform.
- Temboo - Beyond code snippets, into ready-to-use processes, that simply API integration, taking care of authentication, credential management, updates and more
All three of these platforms are bringing together valuable API resources, from multiple sources into not just a common interface, but providing a language library you can use to build apps efficiently across multiple API resources.
Google Apps Script provides access to Google APIs and services, but recently opened up scripts to acts as connectors, that can be developed by 3rd party providers. Temboo has over 100 APIs in its library, while Webshell is just getting going with less than 25.
I see what Webshell, Temboo and Google are doing as similar to the aggregation, integration and some times automation we are seeing in other trending API areas, but these approaches are actually building languages that allow you to be more expressive with not just single APIs, but fluently with many APIs at once.
This area is new and emerging, and I’m still working to understand the different approaches. let me know if you if you have anything I should be looking at or other thoughts.
More to come...
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Showcasing Your API Integrations With Other Platforms
- Increasing The Focus On APIs In Higher Education Is Important
- Getting To Know Mike Amundsen For The API Craft 2014 Detroit Hypermedia Panel
- The New StrongLoop API Server Provides A Look At Future Of API Deployment
- Models For API Driven Startups Built Around Public Data
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs
- Applying APIs.json To API Discovery In The Federal Government
- The Power In API Discovery For APIs.json Will Be In The API URL Type
- Fixing The Machine Readability in API Commons