State of the API: Monetizing API Deployment Is on the Rise
Developers are building more APIs for external use than in previous years, with nearly half of the developers saying they build for external use — an increase of nearly 5 percentage points.
RapidAPI’s 2022 State of the API report surveyed 850 individuals, nearly half of whom were developers. While the majority — 75 % — are working on internal-facing APIs, the number of developers working on partner-facing (49%) and third-party APIs (54%) increased, jumping nearly 5% year-over-year in both categories.
The survey also found that the “API economy” is a top priority for organizations, according to more than three-fourths of developers surveyed. Fifty-nine percent said it was a top priority, with an additional 16.4% responding that it soon will be a top priority.
That may add fuel to IT research firm Forrester’s prediction that more business leaders will leverage APIs in the coming year.
“They’re going to start getting requests from the business saying …‘Build me that data API that I wanted, build me that transaction API that I wanted,’ and developers are going to be tasked to build those various pieces alongside the APIs that they’re working on,” Chris Gardner, research director, told The New Stack.
The number of organizations monetizing APIs in 2022 is up around 5% compared to previous years, RapidAPI noted. This is especially true in financial services, where API monetization is up 16%.
“Developers from industries including financial services, technology, telecommunications, and healthcare reported monetizing APIs at an above-average rate,” the company wrote in its press release. “There is also a marked increase in monetization from people who work in organizations that use over 10 APIs.”
Popular API Languages
APIs: Rest, Webhooks, Websockets and More
Not surprisingly, 69% used REST — a 10% increase over last year. That was followed by the deployment of Webhooks, at 35%, and WebSockets at 30%.
Software engineer Chameera Dulanga defines APIs as distinct from Webhook and Websockets, because APIs originate with the consumer.
“They [APIs] are well suited for applications like persisting state or perform a quick action to receive an immediate response from the backend operation,” Dulanga wrote. “However, if the server needs to communicate back to the browser, there is no direct method when using APIs unless the browser periodically checks for any updates.”
It can do this by report generation or polling continuously, but WebSockets are better for dealing with this real-time challenge, because they allow “a persistent and bidirectional communication between the consumer and service provider,” he stated, adding that modern browsers all support WebSockets.
WebHooks — sometimes called reverse APIs — are “mostly used to communicate between servers or backend processes,” and, for instance, come into play when you need a push notification — such as on mobile deployments, according to Dulanga.
“WebHooks provides a solution for the overkilling issue in WebSockets by providing a disconnected mechanism to receive a response originate from the service provider,” he wrote.
The other API tools ranked lower than 30% usage, with 27% using AsyncAPIs, 25% using serverless or FaaS, and 23% using SOAP. GraphQL, Kafka and gRPC each received less than 20% of the responses.