Posted on 03-15-2012
I’m going through hundreds of APIs and curating a list of APIs, for what I’m calling the API Stack. The API Stack consists of APIs that provide clear value for developers and have demonstrated real investment in their API, and are in it for long haul.
There are quite a few things I consider when looking at an API, here are a few:
- Value - The API offers clear value to developers, without needing an explanation.
- Web API - They don’t have to be 100% REST, but web APIs make developers lives easier.
- Active Blog w/ RSS - A blog is a quick way to see what is behind the curtain of an API. If they care enough to have a blog, and communicate with developers, and keep it active it demonstrates they care. With an RSS feed I can programmatically understand whether they are active or not.
- Active Forum w/ RSS - A forum gives developers a voice and also shows an API owner cares what developers thinks, and is willing to support a large community. An active forum is a positive sign of an API, and the RSS feed also gives me a programmatic way to assess.
- Twitter - An active Twitter presence is a pretty key metric in understanding the value of an API. If the company has the resources to actively engage developers via Twitter, they care. And again I can programmatically monitor and see if someone exists behind the API.
There are other metrics I use, but these are proving to be the most positive characteristics of an API that developers can depend on. Many APIs I come across don’t even meet these basic requirements. What triggered this post, was I had just looked at about 10 APIs that did not meet these basic requirements, and then I came across one that clearly met all of these, and more--GeoIQ.
GeoIQ has a mapping API that provides clear value to developers, and its obvious they are investing the necessary resources, so the API is successful. So I’m adding GeoIQ to my API stack under the category of “local”.
If you feel your API is a good fit for the API stack, make sure and ping me.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- 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