Posted on 10-24-2011
As the number of APIs grow, the number of ways in which API owners control and incentivize their developers ecosystems evolves. APIs are your business development 2.0 platform, and it is up to you to tailor your services to incentivize your developers as well as control API usage to meet your business goals.
One emerging way to control API consumption to meet your business goals is through a balance between pricing and terms of service (TOS). By offering branding opportunities to developers that they can deploy alongside the content and resources they consume via your API, you can easily turn your developer community into an extension of your marketing department.
Price breaks can be offered to developers who extend your brand, encouraging them to build a business around your API content and resources as long as it adds value to your brand. API consumers who opt not to take part in branding, can be charged more, adding value to your company purely as revenue opportunity.
Branding and pricing controls are a growing way to ensure your API adds value to your company either as revenue or brand syndication, but another way some content and data API providers are finding success, is through a contribution incentive. Just like brand extension, API contribution gives developers an opportunity to participate deeper and receive price breaks, while also be encouraged to contribute content back to an API, enriching content and add valuable information back to your companies API.
Writeable APIs can be made available allowing developers to contribute user reviews, comments, annotations or even correct and update content that originated from your company. Proper service and key management around your API, allows you to track which users contribute content back to your system. As a result of this participation you can offer further price breaks in the form of credits, or even end up paying customers for their content contributions.
Incentivizing and controlling API usage through brand, pricing and contribution may not work for every API, but it offers some interesting opportunities for publishers and API owners to develop new forms of self-service, business development relationships around their API ecosystems.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- 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
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs
- Applying APIs.json To API Discovery In The Federal Government
- The Power In API Discovery For APIs.json Will Be In The API URL Type
- Fixing The Machine Readability in API Commons