Review my startup idea: One API to rule them all.

"One thing I haven't found, however, is one API that lets the skilled developer manipulate and search multiple APIs at once."<p>There is one, it is called "the internet"

Singly's working on this, especially as it applies to personal and social data: <a href="http://singly.com" rel="nofollow">http://singly.com</a>.<p>[Disclosure: I work at Singly]

Will you do it for non-developers like<p><a href="http://Zapier.com" rel="nofollow">http://Zapier.com</a>, <a href="http://IFTTT.com" rel="nofollow">http://IFTTT.com</a>, <a href="http://rules.io" rel="nofollow">http://rules.io</a> and <a href="http://elastic.io" rel="nofollow">http://elastic.io</a>, <a href="http://ritc.io" rel="nofollow">http://ritc.io</a> , <a href="http://kynetx.com/" rel="nofollow">http://kynetx.com/</a><p>or more focused on developers like :<p><a href="http://temboo.com" rel="nofollow">http://temboo.com</a>, <a href="http://singly.com" rel="nofollow">http://singly.com</a>, <a href="http://webscript.io" rel="nofollow">http://webscript.io</a>, <a href="http://cloudsnap.com" rel="nofollow">http://cloudsnap.com</a>, <a href="http://script.google.com" rel="nofollow">http://script.google.com</a> , <a href="http://webshell.io" rel="nofollow">http://webshell.io</a><p>What would be your main paradigm and what do you want to bring to the ecosystem?<p>Disclosure : I work for webshell.io and lol to see that your post make reactions of lots of API of APIs company (Singly, Cloudsnap, Ritc.io)<p>If some one in this page wants to reach us for open discussion for making the web programmable in an easier way team[at]webshell.io

Seems like it might touch on aspects of <a href="http://zapier.com" rel="nofollow">http://zapier.com</a> which is a bit more of a mashup mentality but definitely allows you to combine multiple APIs to do interesting things.

Immediately thought of this cartoon: <a href="http://xkcd.com/927/" rel="nofollow">http://xkcd.com/927/</a> ;) &#60;br/&#62; This could be a relevant resource: <a href="http://www.programmableweb.com/" rel="nofollow">http://www.programmableweb.com/</a>

- <a href="http://foauth.org" rel="nofollow">http://foauth.org</a> - <a href="http://developer.yahoo.com/yql/" rel="nofollow">http://developer.yahoo.com/yql/</a>

As far as security is concerned, you probably don't want user authentication like a username/password combo to be passed with the requests, but rather acquire an oauth token that expires after a certain period of time and have specific rights within a scope to read-only vs write based on that token.<p>One question with concurrent API queries is how would you handle the race condition? Say I query 3 APIs at the same time, will I have to wait until the slowest one returns the results to get all results? Will it instead push results to a pre-determined results URL?<p>What are some cases when you would query multiple APIs and want the results at the same time? Why not just wait for each result, parse it myself, then pass some piece of that computed result to the next query, and so on? What would be amazing would be a universal API processor that can do some of this API to API call parsing and processing in the backend, store all credentials, and just get the final results of a long chain of API calls. Now that's something that would make developers' lives easier and I'd pay money for..

A lot of people are trying to fix this right now. A lot of people think that most API's, even though guided by Oauth or Oauth 2.0, are easy to implement, and it's a huge misconception. So many of the API's have quirks and issues all the time, making it incredibly time consuming to implement, learn, and keep up to date.<p>Making the process easier is a huge need right now. There are a lot of apps, and it's all becoming more separated. People want to integrate, and it's a pain in the ass to integrate quickly and cleanly.<p>EmergentOne and Apigee are helping people create standard API's.<p>Zapier and IFTTT are giving you a UI to meld them together.<p>Cloudsnap, Singly, and Webshell are all doing what you're describing, each with a different target of apps. Singly and Webshell are seemingly more social, whereas Cloudsnap is more related to business apps.<p>And of course, YQL, which has been around a long time.<p>--<p>Disclosure: I'm a designer for Cloudsnap, and above is my opinion and not necessarily the views of the company.

I'm not very familiar with them but check out<p><a href="https://www.mashape.com/" rel="nofollow">https://www.mashape.com/</a>

What do you imagine this API would look like if it existed?<p>What use case do you believe it serves (who would use it, what existing behavior would it replace)?<p>If you're going to call this a "startup" then what is the business plan beyond some set of technical features which may or may not be feasible?

For the IdM side of things, there is SCIM:<p><a href="http://www.simplecloud.info/" rel="nofollow">http://www.simplecloud.info/</a><p>It started as Simple Cloud Identity Management, but once it got to IETF, it was changed to "System for Cross-domain Identity Management". This initiative has been backed by Google, Ping Identity, Salesforce, Cisco, SailPoint, UnboundID, and others. You can see some of these names on one of the RFCs:<p><a href="http://tools.ietf.org/html/draft-ietf-scim-core-schema-00" rel="nofollow">http://tools.ietf.org/html/draft-ietf-scim-core-schema-00</a><p>This API is just for identity management, and it has taken years to get to this point. I think it would take many more to get to a common API for everything else.

Reminds me of YQL by Yahoo.

Do you have any use cases in mind ?<p>It seems to me that you would mostly act as a proxy between a user and a service, which really doesn't sound too useful unless one actually needs to access dozens of APIs (which doesn't seem to be something that happens often).<p>Or is your idea really an aggregator (e.g. "find images using such and such keywords" and it returns results from flickr, 500px, ...) ?

Sure, there are over 8,000 web APIs, but how many will be reasonably be within the scope of your project? How many times do we need a weather app that also takes photos, tweets, and gives stock prices?<p>Even though this seems to try to solve that problem, I think it obfuscates whats usable more than the internet does in simply just searching for the API.

Sounds like Yahoo Pipes, or YQL (as already mentioned).<p>Auth should be linked separately from the individual requests if you can. It would be a lot better to auth against $yourService, and $yourService has the cached / OAuth'd credentials for $otherService and handles the auth dance / request signing / whatnot.

You say 8000 APIs, but for example on <a href="http://apihub.com" rel="nofollow">http://apihub.com</a> , you have more than 13000 APIs registered. And OpenAPIs are only the emerged part of the iceberg. Soooooooo many services ran by private APIs in big companies...more than you expect.

See SPARQL and the semantic web, though I think the xkcd cartoon is the better response.

For better understanding why we need an "API to rule them all" you can check the <a href="http://apijoy.tumblr.com" rel="nofollow">http://apijoy.tumblr.com</a> about everyday's developer pain with APIs.

You should take a look at Zapier. They do most of what your getting at.

Have you looked at Yahoo! Query Language? <a href="http://developer.yahoo.com/yql/console/" rel="nofollow">http://developer.yahoo.com/yql/console/</a>

the team behind rules.io are leading an open source API framework project called Geekier which is exactly this. Take a look at the details here in Github <a href="https://github.com/rulesio/geekier/wiki" rel="nofollow">https://github.com/rulesio/geekier/wiki</a> - there is a link to the Google group for the project as well.

Look at <a href="http://webshell.io" rel="nofollow">http://webshell.io</a> I know they are hiring! ;-)

Like Zapier?

In what way does this simplify joining data from multiple APIs?

a certain xkcd comes to mind.