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
- Hypermedia Feels Like We Are Still Learning To Communicate With APIs
- Getting To Know Markus Lanthaler For The API Craft 2014 Detroit Hypermedia Panel
- Getting To Know Kevin Swiber For The API Craft 2014 Detroit Hypermedia Panel
- Getting To Know Steve Klabnik For The API Craft 2014 Detroit Hypermedia Panel
- New Indix API KickStart Program Reduces Costs For Developers
- Getting To Know Mike Kelly For The API Craft 2014 Detroit Hypermedia Panel
- A Shared, Distributed Experience(Metrics) Layer For The API Driven Application Stack
- Showcasing Your API Integrations With Other Platforms
- Increasing The Focus On APIs In Higher Education Is Important
- Getting To Know Mike Amundsen For The API Craft 2014 Detroit Hypermedia Panel
- The New StrongLoop API Server Provides A Look At Future Of API Deployment
- Models For API Driven Startups Built Around Public Data
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks