B2B growth and sales · Difference-in-differences, synthetic control, instrumental variables using API-network variation, and private API data.
How APIs Create Growth by Inverting the Firm
Benzell, S. G., Hersh, J., & Alstyne, M. (2023). How APIs Create Growth by Inverting the Firm. Management Science.
Plain-English take
In this study, Public API adopters grew an additional 38.7% over 16 years relative to similar nonadopters; growth was stronger with more complementors and network centrality. Internal-only API use had no significant effect, while public APIs increased breach risk. Founder use: Treat an API as an ecosystem product: measure active complementors, connected apps, centrality, and partner value—not only API calls—and budget for security controls.
How much weight to give this
4.0/5 Useful empirical evidence with context-specific transfer limits
The 1–5 evidence-check score is a practical reading aid, not a formal peer review or a probability that a conclusion is true. It combines design strength (2 points), sample reporting (1), comparison/control clarity (1), and how much of the paper could be checked (1). Access affects how confidently this directory can assess a study, not the study's underlying quality. Blinding is reported separately because it is not relevant to every design.
Design description was checked against the directly fetched article source; conclusions remain specific to the studied setting.
Sample size or the source's lack of a reported count is stated explicitly.
The comparison or identification strategy is described from the article record.
A directly retrieved full paper is available.
Double-blind? Blinding is not stated in the source reviewed; that does not establish whether blinding was or was not used.
Research question
What the authors investigated
Do public APIs create firm growth by enabling third-party complementors, and what are the security trade-offs?
Design
Difference-in-differences, synthetic control, instrumental variables using API-network variation, and private API data.
Sample and setting
Public firms adopting public APIs, API-network data from 2005 onward, and a private API development firm's data.
Reported result
What the study found
Public API adopters grew an additional 38.7% over 16 years relative to similar nonadopters; growth was stronger with more complementors and network centrality. Internal-only API use had no significant effect, while public APIs increased breach risk.
This is a paraphrase of the source. Check the original paper for definitions, estimates, statistical uncertainty and analysis details.
Scope and transfer
Limitations to keep in view
Firm-level observational designs still depend on identification assumptions; public-company/API adopters and market-value outcomes may not map to early-stage private SaaS.
Possible founder application
Treat an API as an ecosystem product: measure active complementors, connected apps, centrality, and partner value—not only API calls—and budget for security controls.
Evidence access
Open full text captured directly
Publisher page directly retrieved with Firecrawl; scrape reference 01a1227f-25d8-722f-8628-9d5191c591cd. Claims are limited to the reported article record. Correction notices were not separately checked.
If only an abstract or metadata was available, the profile is limited to claims supported there. A paper's paywall does not change its evidentiary status, but it limits what we can substantiate from accessible text.