Posted on 07-24-2014
I saw two tweets from Zapier the other day, where they were highlighting two separate SaaS platforms, who had integrated Zapier into their own platform. Both Gumroad and Hall took the time to highlight the other platforms they are integrated with. I think there are a couple of interesting items in these stories…
Zapier & IFTTT Integration
A while back I added reciprocity to this list of API management building blocks, because I was seeing enough API providers, taking it upon themselves to make sure their platform had both Zapier and IFTTT integration. Ensuring your API is working with leading reciprocity providers will become even more critical for API providers, as more non-developers are putting APIs to work managing their daily personal, and professional lives.
Dedicated Integration Page
The fact that hall has a dedicated integration page is interesting. I think it is valuable to show the platforms that an API has been officially integrated with. It helps developers, and non-developers understand the potential that exists around a platform and its API. I can also see the benefit of opening up the ability for the API ecosystem to submit their own integrations as well--you never know it might encourage other platforms to integrate, if they know they have an opportunity to be showcased.
I like how Hall does their integration page, and they 15+ integrations, they have a custom option, which is basically their very simple API, allowing you to post messages from your app. Hall doesn’t seem to have a full blown API, allowing you to interact with all aspects of the platform, but I still their approach is interesting.
I think that integration with reciprocity providers like Zapier and IFTTT should be default for all API providers. I also think that API providers should consider highlighting other common platform integrations like with Heroku or Github, depending on the nature of your API. You can consider providing seamless integration between platforms, as well as what I’d consider a platform development kit (PDK)—providing open source, white lable code that allows a developer to reverse engineer your integration with other leading platforms.
As we spend more time in the clouds, I think providing seamless integration with other platforms, providing platform development kits (PDK), and employing reciprocity providers like Zapier and IFTTT will become the norm.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- 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