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
- Providing Users With Reciprocity Tools So Important Intuit Purchases itDuzzit
- Bing Developer Assistant for Visual Studio Delivers Relevant API Code
- Average Number of APIs Used In A Modern App
- An APIs.json Collection Of API Resources Across Your Public, Partner Or Internal Resources
- One Possible Reboot Of The API Stack
- How Are Dev Shops In Chicago Using APIs? A Talk With Bryson Pouw At Blaze Portfolio
- Every API Provider Should Have A Logo And Branding Page
- What Is An API First Strategy? IT architecture And Catalyst For Engagement
- The Speed Of Federal Government When It Runs On Github
- Swagger, APIs.json, And Review For The New Developer.Trade.gov
- Student, Instructor, Classroom, Class, And Course API Planning At BYU
- Can You Add My API To Your Website Listing?
- Adding Google To List Of API Deployment Companies
- What Is An API First Strategy? Adding Some Dimensions To This New Question
- The Five Month Journey Toward A Stable APIs.json Discovery Format
- How Are Mobile Dev Shops In Chicago Using APIs? A Talk With Dave Devitt At SYDCON
- An API Case Study Format From Google Cloud Platform
- Next Stable Version of APIs.json + APIs.io Is Ready - Are Your APIs Discoverable?
- Expanding API Gateway Connectors Into A World of API Deployment Startups
- Where The Good IPAs Are In Chicago While At API Strategy And Practice In September
- The Blog For Your API Is The Most Important Signals You Can Send
- Public APIs Are Tough When You Are In A Tightly Controlled Industry
- Give Me A URL To Request Then Store My API Keys In My Private Github Repo
- Mapping The World Of Internal APIs Via Rogue API Registry
- Continuing With The API Restaurant Analogy