Posted on 02-26-2014
I’m working with the Cashtie API to pull together an API evangelism strategy for the payments API. As I pull together, it seems like a great opportunity to share with you. Who knows, maybe you can use some of the elements in your own API strategy.
Next up is developer engagement, and focusing on the ways you reach out to API consumers. You don’t need to describe every way you are going to engage with developers, but you should make sure and pick a handful of channels and stick with them, regularly reaching out to developers, providing a communication platform they can depend on.
There are some proven approaches to developer outreach:
- Fresh Engagement - Emailing new developers who have registered to see what their immediate needs are, while their registration is fresh in their minds
- Active User Engagement - Reaching out to existing, active users of an API and find out what they need. Profile them, including Twitter, Facebook, LinkedIn and pull any profile information, then grade and categorize each developer
- Historical Engagement - Emailing historical active and / or inactive developers to engage and understand what their needs are and would make them active or increase activity, consider newsletter or personalized emails when appropriate
- Social Engagement - When emailing any developer, using Rapportive you can establish any URL, Twitter, Facebook or LinkedIn profile they have and reach out via these networks
There are many other ways to reach out to developers, but you should have a regular rhythm for reaching out to new developers, existing developers will re-enforce relationships with your developers consistently through the channels that make the most sense.
If developers know they will get regularly information from you via a newsletter, and that you are accessible via common social media channels, they are more likely to reach out when they need help, and have you in the back of their mind when they do encounter a problem that your API provides a solution to.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- 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
- Andrew Nacin Of WordPress @APIStrat Chicago
- Push Button API Deployment With The Heroku Button
- WordPress Style API Modules For Government
- The Heroku HTTP API Design Guide
- What I Have Been Calling API Trends, Are Slowly Being Baked Into API Operations
- FDA Finding Their API Mojo With A New Drug Label API
- Adding PokitDok To Healthcare Research And The API Stack (Well They Did)
- Why I Am Continuing To Integrate Zapier In My Business Workflow
- Who Is Going To Build The Uber API Platform For The Sharing Economy?
- The API Focused Dev Shop
- Route SMS Messages To Google Spreadsheets Via Twilio API With TwilioSheet
- Publishing Your APIs To Product Hunt
- 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