Skip to main content

Command Palette

Search for a command to run...

A Visual History of APIs

Published
•2 min read•View as Markdown
A Visual History of APIs
D

In my free time I like to play with APIs and build small projects to feed my curiosity. Also a classically trained artist, I love to communicate my ideas visually sometimes on a canvas and sometimes through a flow chart.

evolution of video conferenceing (6).png We have come a long way since Roy Fielding's famous dissertation on REST and a handful of emerging technology companies like Salesforce, eBay, and Amazon leading the way to the definition of web APIs we use today. Over the years we saw how Amazon web services laid the foundation, while some APIs like Flickr failed. By 2014, Obama's white house was launching APIs to enable the voice of democracy with APIs.

The launch of the iPhone in 2007 created the opportunity for the API economy to shape where products like Uber could be built using Google Maps APIs.

In 2014 we saw the arrival of tools like Postman and Github enabling developers to discover, evaluate and integrate with new APIs faster than ever before.

By 2015 there were news titles such as Why APIs will save your business from getting “Uber-ed”.

In 2022, we are seeing the evolution not just in more APIs being launched but also the jobs and functions evolving around shaping great API experiences. API Product Management has become a specialization and so has developer relations/developer evangelism. Customer support function has also evolved to serve API products (I talk about support models in my blog Driving meaningful customer impact with API Governance).

Did I miss something? Share your thoughts in the comments.

References

M

Awesome infographics Deepa. I am a test auzomation engineer so I deal with APIs daily. I followed you to make sure I won't miss any of your posts. 😊

1
D

Thanks Miki! Would love to learn what are the APIs you use more often?

10
M

At the moment at work I only use our internal API but in the past I have integrated many cameras into our Video Management Platform via REST and Soap APIs. Believe me, it was a hell. Every camera vendor had their own APIs and many vendors had multiple APIs. Later the industry came up with a soap based standard called ONVIF, but it was not conrete enough and we again had to integrate the cameras one by one. 😊Deepa Goyal

D

I am sure Camera APIs will also evolve with the buzz around IoT. Miki Szeles

10
M

Well we will see. In my opinion using soap instead of REST was a bad decision. Deepa Goyal 😊

More from this blog

O

One sprint at a time - A blog about design, analytics, development and product management.

21 posts

Deepa Goyal is a product strategy leader, API expert, and author with 15+ years at Twilio, PayPal, and Postman. She specializes in API strategy, developer experience, and product-led growth.