Posted on 09-29-2011
Historically APIs are deployed to provide data and resources to business partners. However, in the last 5 years we have seen a shift in focus to also delivering more open, publicly focused APIs, based upon the success of popular services like Google Maps, Twitter and Twilio. In the last year, many companies are also seeing the benefits of deploying and consuming APIs internally, in addition to partner driven, and open public APIs.
3Scale, Apigee and Mashery all advocate for evaluating the deployment of APIs for internal and partner consumption as well as carefully weighing the value of a public facing API ecosystem. As an API evangelist I aslo have found the need for equal distribution of resources when it comes to evangelizing the benefits of APIs as well.
- Internal API Evangelism - I spend ⅓ of my time educating internal departments from IT to marketing about the benefits of APIs. I want everyone to understand that APIs will make our company more flexible and nimble, and help us out-maneuver our competitors. APIs also will assist us in delivering mobile content and applications within our company and to our customers.
- Partner API Evangelism - I spend ⅓ of my time educating our partners about the various APIs we have, how they can be used, and provide as much material as I can about our web services. I also evangelize about other APIs that compliment our services and can provide benefits to our partners. Its not just about selling our partners on our services, its letting them know we are invested in their success.
- Public API Evangelism - I spend ⅓ of my time blogging, tweeting and generating code samples, prototypes and any other materials that will help get the word out to the public about our APIs. Public API evangelism is not just about SEO content, its about social engagement. Reaching out to developers and companies where they already frequent, making sure I listen, participate and add value to those communities on behalf of my company.
APIs are not just an external interface. Although they do offer tremendous benefits when interacting with the public or sharing information and resources with your most valued partners, they can also make your company operate more efficiently.
API evangelism shouldn’t be just about reaching out to your public or partner developers. Your API evangelism strategy should also focus internally within your company and across all departments. Make sure your API evangelism strategy is equal parts internal, partner and public outreach and eventually you will find the success your looking for.
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