2024 State of the API Report
2024 marks the 6th year of the State of the API—the most comprehensive survey on APIs with over 5,600 developers and API professionals sharing their thoughts this year.
Share
The rising shift from code-first to API-first
74% of respondents are API first in 2024, up from 66% in 2023.
APIs front and center
APIs are no longer an afterthought but the foundation of development, with between 26 and 50 APIs powering the average application. The API-first paradigm prioritizes API design, streamlining integration and boosting efficiency across teams. To deliver top-tier APIs, engineering organizations are realizing they need more than just an API gateway. Proper tooling, enablement, and processes are essential to building and scaling high-quality APIs.
API-first yields tangible benefits
When APIs are the core of development, the advantages are clear:
Faster API production
Last year, 47% of developers could produce an API within a week. This year, that number jumped to 63%.
Rapid failure recovery
API-first organizations recover from API failures faster, often within an hour.
Rising API production speed
Faster, faster!
67% of teams using Postman team workspaces can produce an API in less than a week, compared to 58% of those who don't use workspaces. This improvement highlights the power of collaboration within dedicated API workspaces.
Collaboration challenges: The hidden bottleneck
Despite faster production, developers still face hurdles when collaborating on APIs.
Documentation issues, complex requests, and unclear variables can delay public and private API integration. Inconsistent onboarding processes can extend the time it takes to get started on even the simplest API use cases.
58% of developers rely on internal documentation, but 39% say inconsistent docs are the biggest roadblock.
Pro tip
Postbot now generates comprehensive API documentation with a single click, saving developers hours of manual work and keeping docs up-to-date.
44% of developers dig through source code to understand APIs, but over half collaborate with product managers, QA, and designers who can't always interpret the code.
Pro tip
Postman Workspaces enable smooth collaboration by centralizing API-related information, saving time across the board.
43% of developers rely on colleagues to explain APIs. What if that colleague is in a different time zone? This can cause frustrating delays.
Pro tip
Postman Workspaces store critical API information where the work happens, enabling asynchronous collaboration.
Scattered conversations: The collaboration breakdown
API changes—whether additions, edits, or deprecations—are a routine part of development.
However, without proper tools to manage these transitions, teams face challenges that lead to inconsistencies, breaking changes, and potential security risks.
44% of developers rely on chat tools or email for API development, but critical updates can easily get lost in the mix.
Pro tip
The Workspace Updates Feed ensures everyone stays informed. Post updates and notify everyone watching the workspace. Future integrations will pipe those workspace updates automatically into Slack and Microsoft Teams for new change alerts that are always stored in your workspace, ensuring no important changes slip through the cracks.
Gateways are multiplying: A new era of API management
The traditional single-gateway model is becoming obsolete. Now, the market demands support for all types of APIs—whether private, partner, or public—regardless of the gateway in use. Nearly a third of API publishers use multiple gateways, reflecting the complexity of managing APIs in diverse environments. However, multiple gateways can cloud API discovery and observability, making it harder to monitor APIs effectively.
Pro tip
Integrated API management platforms offer a consolidated view of APIs, regardless of their gateway. These tools streamline API discovery, observability, and security, reducing fragmentation.
APIs as revenue drivers: Monetization on the rise
APIs are no longer just technical enablers—they are revenue-generating products.
62% of respondents report working with APIs that generate income. This signals the rise of the API-as-a-product model, where APIs are designed, developed, and marketed as strategic assets.
Why it matters
APIs are opening new streams of revenue for organizations through public-facing services and partner integrations. As part of broader product strategies, they enhance internal efficiency while also driving business growth.
Pro tip
Launch, distribute, and grow your APIs with the Postman API Network, where consumers can onboard in minutes and deliver real-time feedback.
AI landscape diversifies
AI tooling is on the rise, and OpenAI will remain at the top. Developers will also be looking to diversify AI tooling, models, and deployments with AI tools from Meta, Google, and Perplexity.
Pro tip
The age of AI is powered by APIs. The rapid adoption of chatbots like ChatGPT has proven that AI bots are going to advance the state of human-computer interaction. AI alone won't boost productivity—you need quality APIs to stay ahead in modern software. Until now, we have primarily been designing APIs for humans, but designing APIs for machines will become an increasingly important area…. and AI alone won't boost productivity—you need quality APIs to stay ahead in modern software.
Key insight
Biggest AI integration pain point: Security and compliance.
API observability & security: Addressing the new attack frontier
APIs are now a top target for malicious actors, making security and observability critical.
As companies continue to embrace an API-first approach, maintaining high standards for internal and external APIs is crucial to preventing exploitation and maintaining performance.
API key vault security tools
Shockingly: 27% do not use API key vault security tools, while those who do favor AWS Key Management (28%) and Azure Key Vault (24%).
The challenge
Without proper observability and governance, APIs can become vulnerable entry points for cyberattacks. It's essential for organizations to monitor their APIs to prevent security breaches and maintain operational integrity.
Pro tip
Postman Vault now integrates with external vaults like AWS Key Management, Azure Key Vault, and HashiCorp Vault. You can link secrets directly from these external systems into your Postman environment, streamlining security processes and removing the need for manual secret management.
API ownership: Who's in charge?
API creation and management vary depending on the organization's structure. Here's how teams approach API development:
48% of respondents say API creation is owned by the development team, driven by demand.
48% say a central team oversees API strategy and governance, ensuring consistency across projects.
Furthermore, 40% of all respondents report a business-oriented directive guiding API development, with a focus on revenue generation and external partnerships.
Key insight
Some companies are still leveraging an Architect to drive API design through governance and control, but this alienates the person who actually designs the API—developers. The de-centralization of API design is on the rise and Postman Collections have become the tool of choice as they enable the generation of API workspaces—then enable design time governance.
Conclusion: The API-first future
The shift to an API-first approach continues to revolutionize how development teams work. From faster production times and better collaboration to enhanced security and API monetization, organizations that embrace this model are setting themselves up for long-term success. By prioritizing API design, governance, and security, teams can unlock new opportunities, deliver APIs faster, and ensure their APIs are protected and optimized for the future.