TechForge

29th September 2020

Postman’s State of the API report for 2020 suggests that investments have remained strong despite the challenging economic climate.

The report is the most comprehensive survey of the API industry—surveying a total of 13,586 developers, testers, executives, and others.

Abhinav Asthana, Co-founder and CEO of Postman, says:

“Our annual survey reveals that the API ecosystem is expanding, investments are flowing, and momentum for an API-first philosophy is being embraced more and more.

The data also shows us the importance of APIs and their role in responding to sudden and tectonic shifts in the way businesses, governments, and nonprofits operate, including pandemics.”

Almost half of the respondents claim that investment and resources into APIs will increase over the next 12 months. Another third say that investments will remain about the same—which is still heartening given the wider economic and social devastation reaped by the ongoing pandemic.

Software developers are among the most prepared to adapt to things such as remote working. According to the report, 89 percent said their organisations are offering remote work as an option following the pandemic.

An increasing number of developers worked remotely even prior to COVID-19 and separate research suggests the majority expect that to continue.

More people than ever are relying on software to work, play, and stay in touch—so the continued confidence in investing in API development is perhaps unsurprising.

Close to a third (30.6%) of respondents to Postman’s report said that APIs played a pivotal role in their own business’ ability to respond to the pandemic by facilitating customer communications, powering remote work options, and quickly responding to regulatory changes and government initiatives.

However, the research highlights some speedbumps in the development and usage of APIs. 52.3 percent say that lack of time is the main challenge in producing APIs, while 54.3 percent report a lack of documentation as the key problem in using them.

API developers want to spend more time designing them (ideally 11% of their time) and automating testing (15%) than debugging (10%). Currently, they say they’re spending just 8.7 percent of their time designing APIs, 11 percent automating testing, and 17 percent debugging.

REST (93.4%) is the dominant architectural style for APIs, followed by webhooks (34.4%), SOAP (33.4%) and GraphQL (22.5%). JSON Schema (75.6%) is the dominant API specification, followed by Swagger 2.0 (43.9%) and OpenAPI 3.0 (27.8%).

Respondents are most excited (48.7%) about microservices in the future, followed by Kubernetes (43.6%) and containers (42.2%).

In a year that’s been interesting, to say the least, Postman’s report is a fascinating insight into the health of API development (and, by extension, the wider development industry.)

You can find Postman’s full State of the API report here.

(Photo by Clay Banks on Unsplash)

Interested in hearing industry leaders discuss subjects like this? Attend the co-located 5G Expo, IoT Tech Expo, Blockchain Expo, AI & Big Data Expo, and Cyber Security & Cloud Expo World Series with upcoming events in Silicon Valley, London, and Amsterdam.

About the Author

Senior Editor

Ryan Daws is a senior editor at TechForge Media with over a decade of experience in weaving narratives and dissecting complex topics. His articles and interviews with industry leaders have earned him recognition as a key tech influencer from numerous organisations. Under his leadership, publications have been praised by analyst firms for their excellence and performance. Connect with him on X, Mastodon, Bluesky, Threads, and/or LinkedIn.

Related

20th August 2026

19th August 2026

17th August 2026

12th August 2026

Join our Community

Subscribe now to get all our premium content and latest tech news delivered straight to your inbox

Popular

20090 view(s)
10270 view(s)
5817 view(s)
5482 view(s)

Subscribe

All our premium content and latest tech news delivered straight to your inbox

This field is for validation purposes and should be left unchanged.