our words.

Someone always has something insightful to say.

Adam Kleinberg

Digging deeper on Brand APIs

by Adam Kleinberg

Digging deeper on Brand APIs

Earlier this week, I wrote an article on Mashable calling for brands to consider developing their own APIs. In it, I used Kraft as an example for how brands could do this. 

A question was put to me by the global head of communications planning at one of the biggest companies in the world:

Can somebody use that Kraft example and let me know how the api they described would work? How and where would a consumer be able to "type in any ingredient and get back a list of recipes from Kraft?"

My answer.

Think of Twitter. They have a 140-character form field on their website. They have a feed. These pieces of functionality are services that you can consume on twitter.com. But they have been constructed in a way that another developer can access the code for one of those services easily, modify it and embed it in another application. Hence, I can put send data to that 140-character form on any website, in Seesmic, via text message, in a widget, etc. Same thing with how that data is pumped back out. That's why I described the API as a hook.

Now, Kraft hasn't done that. My editor challenged me to come up with an example for how a company that wasn't data-driven (like NetFlix for example, who released APIs in a million dollar challenge to come up with a better recommendation engine), so I came up with Kraft. But if you use the Twitter analogy, replace the 140-character form field with an ingredient form field. Then replace the data from your twitter feed with data from the zillion recipes featuring Kraft products in their DB. 

Make sense so far?

There are very different levels of complexity involved with APIs, of course. Take a look at this page containing an overview of FBs Graph API.

http://developers.facebook.com/docs/api

Don't scroll down more than a page because it gets detailed, but what you'll see on the first page or so are snippets of code that you can grab and embed into a webpage to access bits of functionality from the Facebook page.

What I'm proposing is that Kraft (or Unilever) create something like this and allow developers and partners to innovate with it—and yes, even make money from it. Walmart could have a "search for dinner idea tonight" tool on their website. They could integrate the recipes and ingredients APIs from Kraft in it (I added an ingredient API here) so that when mom sees a recipe she likes she could in one click add all the ingredients (including Kraft products of course) to her shopping cart and use Walmart's ship-to-store program so a bag of groceries is waiting for her on the way home from work. 

Walmart wins. Kraft wins.


Tina Hoang

APIs 101. Well done, Adam. The following tangent was brought to mind by Kraft's recipe database. In a recent contest, Culver's essentially let consumers build a branded and searchable recipe database. As the contest is now over, users can still visit the site, interact with the brand, and find their favorite recipe among the 1000+ entries by keyword. http://contest.culvers.com/ Disclaimer: The contest was built on Strutta's platform. Facebook's API was tapped for user authentification and content sharing on the contest site. And heck yes, Strutta has an API! http://strutta.com


Now you say something:

In our effort to prevent spam, we ask that you complete this CAPTCHA before submitting your comment.