Foodspotting is a visual food review and sharing site and application. Unlike other food review sites, Foodspotting lets users review dishes, instead of the restaurant. Along with the review, users can upload a photo of the dish, so other users can see what the dish looks like. Within the site and application, users can search by dish, restaurant, or location.
The Foodspotting API allows developers to access and integrate information and images from Foodspotting. Some example API methods include retrieving and uploading images, searching for and retrieving user information, dishes, places, and reviews, and adding reviews and other information.
When Facebook announced its timeline partners yesterday, there were many familiar names on the list. Some were especially familiar to us because, in addition to now adding their "actions" to Facebook, they also provide APIs to access data created by their users.
Our directory recently passed 4,000 APIs, each one different than almost every other one. There is a single defining factor of all 4,000: in some way, they're available for any developer to use. They're public. There is a virtual ocean below our directory of APIs that are currently private. These APIs drive mobile apps, connect strategic partnerships and exist within organizations large and small to facilitate data sharing.
Some of the APIs in our directory look like cousins of the private API. Their documentation is only available by request, or access is only offered to approved partners. And increasingly, there is a paid barrier to many we list. In some cases, the entire business is an API or collection of APIs.
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.