It doesn’t matter where you turn these days on the web or in the tech blogosphere but you are almost guaranteed to here something about API this and API that. Everything it seems has to have some form of an API available for developers to build applications; whether they be desktop or web based, on top of. The impression that is being given is that without an API you will never be seriously considered as a viable Web 2.0 start-up or even a company looking for a web presence that is trying to hook into the whole social networking scene.

This whole API thing was a subject that Marshall Kirkpatrick looked at in his post on ReadWriteWeb. In the post he asked a bunch of folks at the Web 2.0 Expo what they thought was coming next after this seemingly blind acceptance of ubiquitous APIs. The answers he found broke down to the following categories

• Business models
• Filtering for information overload
• Standards and interoperability
• Outsourcing API services
• Backlash

I found it interesting that he included the idea of there being a backlash against this supposed universal acceptance of APIs but it makes sense if you question whether APIs are truly the end all be all. As more than a few of the people Marshall talked to at the conference suggested that there could be a move away “from the frothy wave of ‘Me Too’ APIs and platform announcements”. As David Janes; creator of Onaswarm, is quoted by Marshall as saying

“How about a return to using well-known protocols (as opposed to APIs) for doing well-understood tasks, i.e. publishing and posting data. E.g. RSS/MetaweblogAPI or Atom/APP…It’s insane…I’ve had more than my fill of working with these APIs.” When I pinged him to confirm those lines – he said that it would more accurately explain how he felt about the APIs he’s been working with if there were some obscenities sprinkled into his quote. That from a man who has put his hand into the dragon’s mouth. If you will.

This whole issue of having to deal with multiple APIs from the developer stand point is easily illustrated with the current drive to develop clients that deal with Twitter and FriendFeed from within a single application. Whether it be within a single application or a multi-window application the problems are still the same – having to deal with two totally separate APIs. This is mind bending enough as it is but what happens when another service comes along that the users want included within that same application framework.

And that is the problem with trying to live within an API based world – everyone will have their own API that at some point are expect to co-exist within the framework of user friendly programs. Then there is the concept of APIs that will talk to other APIs such as is the case with FriendFeed and Disqus. One has to wonder if the point will come where we need an API to manage all the other various APIs scattered around the web.

Then though we get to the whole thing of monetizing these businesses that are so dependant on having APIs. This was the question that Alexander van Elsas’s looked at in his post on the subject today – a must read post in my opinion. For him this freemium business model is nothing more than a dead end that leads to walled gardens and advertisements. Or as he also puts it – it leads to nothing

In most cases it sounds great but leads to nothing. Or as Wired puts it, the ‘I hate Facebook’