2024 State of API Report

API production

Image to illustrate the statistic API issues. Illustration.

While 56% of API changes succeed with minimal issues, a concerning 5% experience failure rates above 25%, highlighting a persistent struggle to maintain stability in production.

Illustration represeting 50% of developers rely on chat tools or email when communicating changes on APIs.

44% of developers rely on chat tools or email for API development, but critical updates can easily get lost in the mix.

How long it takes to produce an API

Over 63% of teams ship APIs in less than a week, while 10% are stuck in a development cycle lasting over 1 month.

Illustration of a star inside a box, symbolizing a key insight.

Key insight

When APIs are the core of development, the faster API production advantages are clear. Last year, 47% of developers could produce an API within a week. This year, that number jumped to 63%.

Less than one hour: 7%
Less than one day: 16%
One day and one week: 41%
One week and one month: 26%
More than one month: 10%

How frequently APIs are deployed

API deployment is speeding up—daily deployments jumped to 8% in 2024, while long release cycles of 6+ months are steadily shrinking. Rapid iteration is becoming the norm.

Hourly to daily: 8%
Daily to weekly: 25%
Weekly to monthly: 35%
Every 6 months: 23%
Fewer than every 6 months: 10%

Most common API testing practices

With 1% admitting they don't test APIs, the real shocker is how security testing lags behind—only 37% prioritize it, leaving APIs vulnerable while integration and functionality lead the way.

Illustration of a lightbulb inside a box, symbolizing innovation.

Pro tip

Only 45% employ performance testing, down from 50%+ in each of the past 4 years. Get testing with easy to use API testing templates.

Percentage of API changes that fail

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.

Illustration of a star inside a box, symbolizing a key insight.

Key insights

  • While 56% of API changes succeed with minimal issues, a concerning 5% experience failure rates above 25%, highlighting a persistent struggle to maintain stability in production.
  • API-first leaders were 25% likelier to say they could restore a failed API in under an hour
Illustration of a lightbulb inside a box, symbolizing innovation.

Pro tip

The Workspace Updates Feed ensures everyone stays informed. Post updates and notify everyone watching the workspace, and 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.

Less than 5%: 56%
5% - 10%: 25%
11% - 25%: 13%
More than 25%: 5%