The API economy is the term for an economic arrangement in which companies package their core capabilities as application programming interfaces and offer them to other developers and businesses as a product. Rather than building everything in-house or installing packaged software, a company can compose its own application out of remote services it calls over the web: payments from one provider, messaging from another, mapping or identity from a third. Each provider’s value is delivered through a programmable interface rather than a shrink-wrapped application.
The model rests on a simple shift in what is being sold. Stripe does not ship a payments program to be installed; its reference describes an API “organized around REST” with “predictable resource-oriented URLs” that other businesses call to move money. Twilio does not sell telephone hardware; its docs present communications as REST resources. In both cases the API itself is the product, and the customer integrates by writing code against it.
This arrangement makes capabilities composable. Because the interface is a stable contract, a developer can wire together several providers and treat each as a building block, much as microservices within a single system communicate over network calls. The result is that a small team can assemble a sophisticated product quickly by buying programmable access to problems that would once have required dedicated engineering and infrastructure.
The economics are visible in how these providers describe and meter their services. Usage is typically self-service and priced per call, per message, or per transaction, so revenue scales with how much other people build. Twilio’s 2016 SEC filing illustrates the demand side, reporting that more than a million developer accounts had registered on its platform, each a potential builder layering new applications on top of the underlying communications network.
The API economy reframes the developer as the buyer and the integrator. Marketplaces, platform ecosystems, and partner directories grow up around successful APIs, and a provider’s commercial fate becomes tied to how easy and reliable it is to build on top of them. That dynamic is why the companies that won in this model invested so heavily in documentation, sandboxes, and overall developer experience: in an economy of interfaces, the interface and the experience of using it are the moat.