About the API Pulse
info
The API Pulse is an ongoing survey of the API space. The objective of this work is meant to provide an ongoing assessment of how APIs are being used across the top 25 industries, providing a vendor neutral approach to understanding what is happening so that we can all make more informed decisions. After contributing to the SmartBear as well as Postman API reports, and seen many other vendor reports come and go, I wanted to see if I could be the change I wanted to see when it comes to APIs.
The goal here isn't to compete with Gartner, but to contrast the vendor approaches to assessing the state of APIs, which tend to reflect the layer of the API space they sell to. The API Pulse spans all the types of APIs out there, and attempts to focus on the experiences that matter most to producers and consumers. When creating the schema for the API behind The API Pulse, I attempted to craft it so that individuals within enterprises can submit, as well as individuals who are independent, or in-between work in any given moment.
You are welcome to fill out as many of the sections as you feel speak to your view of the API space. You will able to submit and update any time, with email validation required each time you submit. When ready, you will be able to see how you size up within your own business sector anytime, and be able to see across all business sector twice a year on May 15th and October 15th. The goal is to incentivize you to submit in exchange for where you fit into your industry, and incentivize you to come back and update to understand where you fit in over time as you and your business sector evolves.
The API Pulse is an API Evangelist project and operated by Kin Lane. I am personally reviewing every submission and happy to answer questions and obtain feedback on the schema, API, as well as the reports. It will take me years to build, but I am convinced over time I will be able to build a trusted source of information regarding how companies, organizations, institutions, and government agencies are doing APIs. I really want to make sure there is a reliable source of information you can use to decide how you approach your APIs, without being put into a sales pipeline. No names and emails of submissions will be shared or sold, they are only to verify your submission, and only aggregate industry information will be published.