Posted on 07-18-2012
Web APIs come in all shapes and sizes. The differences between API authentication, interfaces and data types can be a big challenge when developers work with multiple social networking APIs like Twitter, Facebook and social media APIs like Instagram and Flickr.
Each API tends to run with their own interpretation of what a RESTful API means, leaving developers left with navigating not only the differences between various APIs, but the changes a single API will make from version to version.
Many industry pundits claim this will become unmanageable. I think its the nature of the web API space, and we should leave API owners to do what they do best, rather than forcing them to agree on standards. Then how will we bridge these difference? This is an important opportunity for providers to step in and aggregate critical APIs within specific sectors, and provide a unified interface that developers can depend on. One example of this in action is Singly.
Singly aggregates some of the most important social APIs, simplifying authentication, creating consistent patterns for API endpoints and a unified set of data types to work with across all supported APIs. Singly pays attention to the differences between APIs and versions, so developers can do what they do best--build social applications, using social data from the platforms their users are already on.
Immediately the pundits will ask, how can they keep up with all the changes? I respond with how can we not move this industry forward without someone paying attention to it for developers. I see Singly as a necessary component for the API industry to stabilize and move forward. Developers needing to integrate with a single API can visit the API directly, while developers who need to integrate across multiple APIs can depend on Singly.
I see opportunities for the Singly model to be applied in other niche areas like location based services, video, restaurants and government to just name a few fast growing API business sectors. It’s clear that RESTafarians aren’t going to come to an agreement on a single stand, and API owners are busy providing the data and resources they specialize in, so a unified approach like Singly appears to be a healthy path forward for standardizing APIs, creating a more stable interfac for developers.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- 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
- Evolving How We Approach The API Lifecycle With APIMatic
- APIs Can Open Up Your Company To Outside Ideas
- APIs Are Often Just A Facade That Is Covering Up The Legacy View Of World
- A Mobile Developer Toolkit With The University Of Michigan APIs
- Kicking Off Image Manipulation API Work