Posted on 07-14-2014
It is a pretty basic concept—look at other competing or complimentary APIs in the space, before designing your own. This seems like common sense to me, but I look at APIs for a living, and I’m interested in finding the best API patterns across business or government sectors. Even though this topic seems like a no-brainer to me, I still encounter many folks who contact me to discuss their API strategy, but have not looked at any APIs, in the same genre as the one they are looking to enter--which tells me I should be writing about this topic on a regular basis.
My first advice to any API provider, looking to begin new API effort, is to look at as many of the leading APIs out there, as you have time for. Even if they aren’t in the same genre as your API, they are leaders for a reason, and do many things that you can learn from. If nothing else, at least look at the pioneers like SalesForce, Amazon, Twitter and Google—they know what they are doing.
Secondarily I urge developers to go look at any APIs that are doing the same thing, or portentially exist in the same genre, as your API. If you are doing a bookmark API, go look at Delicious and Pinboard. If you are doing an image API go look at Flickr and Instagram. Even if your API will be slightly different, you should look at all, accessible, patterns, that are similar to what you are trying to do do. Try to understand why these APis providers designed their interface the way they did, and actually make calls against the API, to see what you like, and what you don’t like about their approach.
Once you have looked at all the APIs you can, take the best patterns you found, and make it into your own. Even if you come back around, and still think your API design is superior, you will have learned something through the process—even if you learn what you don’t want to do, or just receive validation of your idea. If you haven’t done your due diligence, looking for other healthy API patterns in the space, you are wasting valuable development cycles, on something that may not actually be innovating, and moving the conversation forward.
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