The Sensis API Challenge is back in July and this time with double the bounty offered. The first challenge that run through May 21 asked developers to create the ultimate Zombie App. The July Challenge wants developers to create the best API Cocktail, which means combine the Sensis API with as many complimentary APIs as you want.
Many game developers aren’t seeing the increase in conversions or revenue they hoped for from the Facebook Credits API. LinkedIn has acquired API-happy Rapportive. Plus: financial data challenges, API vs. RSS and 7 new APIs.
Move over, Instagram API, there’s a new hotness. In a similar way that developers sought out Instagram, photo tagging site Pinterest has its share of API sniffers and unofficial wrappers. That and the official Pinterest API is said to be coming soon.
Somewhere in Austin, someone is likely already organizing the lanyards for the thousands of SXSW badges for the techies next month. And somewhere in Brighton, the small team behind Lanyrd is likely working hard to make sure its social conference directory is ready for SXSW and all the other conferences that overlap their way through June and beyond. And for any developers wanting to build on top of Lanyrd, you’re wondering about the Lanyrd API. It’s late. And coming soon. Maybe.
Public APIs have given rise to applications that we could not have imagined a few years back. All the stakeholders in the API ecosystem have benefited, right from organizations providing public APIs, to API consumers and the end user that has been given mashups that combine the best of many APIs. However positive this may sound, it is important to look at instances where APIs end up playing spoilsport in their own little way. This post tries to explore some of them.
Popular room rental service AirBNB does not yet have an official AirBNB API. But signs point to one’s existence, as well as an affiliate plan in place to pay developers for reservations booked through the API. If the company sticks with the plan as written now, developers will be able to make up to 10 million API calls per day before contacting AirBNB.
Food-sharing mobile photo app Foodspotting had an API since day one. Of course, every mobile app has an API, at least if it needs to store or retrieve non-trivial data. Most of those interfaces stay hidden away, private APIs with only that single, internal audience. Foodspotting, on the other hand, signed Zagat as an early partner and now also has OpenTable, among others, using its Foodspotting API. The company is not exactly making it widely available for any developer, though the documentation is public, planting it in a vast grey area that’s becoming increasingly common.
The cloud came tumbling down for many startups and sites based on the Amazon EC2 API today. There’s a perception that storage and scaling in the cloud is supposed to mean we don’t have to deal with outages. It’s pretty clear that’s not actually the case, as some popular sites like Heroku and Foursquare nosedived.
With the recent unveiling of Facebook comments, many have questioned the future of Disqus, the previous comment widget darling. There are some advantages to each, but something Disqus definitely has going for it is its
Disqus API, as well as other features like email moderation.
In the past months we have covered real-time client push services and seen the introduction of real-time client push technology and APIs to a number of services such as Superfeedr and DataSift. This focus on real-time push to client applications, and in particular web browser applications, is very exciting. The initial assumption would be that this movement has been triggered by an advancement in technology, and to some degree that is the case, but it might surprise you to know that the ability to push real-time updates into a web browser isn’t new and has in fact been around for a number of years.