Posted on 06-01-2012
Many "public APIs" are launched with well, very "public" intent--to extend the reach of the brand and platform. Many of these APIs are setup to pull data, enabling developers to use it in their applications for free or paid, with the understanding they’ll properly attribute the source.
Many of these APIs like Amazon E-Commerce, eBay, Google Places and Foursquare are engineered to publicly extend the central platform, all feeding back back to the “mother ship”, either through linking or other type of attribution.
As the Internet evolves, and the era of "big data" takes hold, and as the need for processing data and deriving meaning out of the flood of data available to us online grows--so does the demand for API access that isn’t marketing centric.
As a big data developer I may be comparing product pricing from Amazon to auctions on eBay, and I may need to use Google Places data to identify best places to sell my products, and Foursquare to identify local demand. The needs of big data API developers are going to be radically different than maybe your originally intended developer audience.
Hopefully you are already carefully targeting your developers and grouping them by their usage patterns. Have you identified any users that are actively using your APIs, but not necessarily following regular patterns? Have you reached out to them?
It might be the case that your API won’t be of interest to big data developers or quite possibly that this isn’t a market you're interested in. However it is a question every API owner should ask--is my API big data ready?
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems
- APIs That Do One Thing And Do It Well Like ZipLocate
- Which API Do I Need?
- The Expanding API Conference Landscape
- Ocotoparts Open Source Google Spreadsheet