Have you ever been stumped how to design a Web API? There are so many different approaches that you can take for even simple things, like paginating API result sets. If you list out your options, it can be easy to end up in analysis paralysis.
I like to remind myself that I’m not the first person to tread on this soil. I often take inspiration on design choices from well-known APIs, assuming that the hard work has already been done. But I realized lately that I’m not confident what a popular or successful API is, and that I have my own exposure biases in what is popular or successful. So, I decided to do some research to address that.
I defined an API’s success and popularity based upon whether it is supported by integration solutions. Integration solutions are systems which allow for the easier connecting or APIs together. I figure that if a service or API is popular, customers will demand it be available in integration systems that they use. As a result, the supported APIs could be correlated to determine the most popular APIs for integrating with.