The platform is the central political-economic structure of the digital age, and APIs are how platforms exert their power. A platform is a business that creates value by mediating between parties — developers, users, partners — and APIs are the technical interface through which that mediation happens. The platform’s power comes from its position in the middle: it controls access, sets the terms, captures the value, and can grant or revoke the ability to participate. I’ve spent fifteen years watching platforms use their API as both an invitation and a leash — opening it to attract developers and build an ecosystem, then tightening it to extract value and exert control once the ecosystem has formed. The politics of platforms is the politics of this asymmetric power, and APIs are where that power becomes concrete. Understanding platforms politically means understanding that the API is the mechanism through which the platform governs everyone who depends on it.
The open-versus-closed choice is where platform politics begins, and it’s never as simple as it sounds. I wrote in 2011 about open versus closed APIs, and the deeper truth I came to is that the choice is really about how much control the platform wants to retain. An “open” platform API attracts developers and builds an ecosystem, but openness with terms of service is still conditional — the platform decides how open, and can change its mind. The fundamental tension between API owners and consumers, which I wrote about in 2012, is the power asymmetry at the heart of every platform: the platform holds the data, the access, and the right to set and change the terms, while the consumer holds only the right to accept those terms or walk away. And walking away is hard once you’ve built on the platform. The open-versus-closed framing obscures the real question, which is always: who holds the power, and what can they do with it?
The platform lifecycle is the recurring political tragedy I’ve documented over and over. The pattern: platform opens its API, developers build a thriving ecosystem, the platform captures the value that ecosystem creates, and then the platform tightens or closes access once it no longer needs the developers. I wrote in 2015 about APIs being used to close rather than open the internet — the dark inversion of the early API dream, where the API that promised openness became the mechanism of enclosure. The many ways in which APIs are taken away, which I catalogued in 2019, are the tools of this platform power: deprecation, price increases, rate-limit tightening, feature removal, and outright shutdown. The platform giveth and the platform taketh away, and the developers who built on the promise of openness discover that the platform’s openness was always contingent on the platform’s interests. This is platform power in its most concrete form: the unilateral ability to change the terms of everyone’s participation.
Twitter is the canonical political case study of platform power, and I’ve written about it more than almost any other platform. Twitter built one of the great developer ecosystems on its open API, normalized third-party API access as a model for the industry, and then systematically dismantled it — restricting access, competing with the apps built on its API, and eventually pricing the API out of reach. I called Twitter the most important API in 2023, partly because its arc so completely illustrates platform power: the rise that depended on developers, and the fall that betrayed them. “Don’t make the same mistake as Twitter did with their API” became a phrase with many meanings, as I wrote in 2017, because Twitter’s API mismanagement was a master class in how platform power, exercised carelessly and self-interestedly, destroys the very ecosystem that made the platform valuable. The subtle ways power asserts itself in API engagements, which I wrote about in 2017, are everywhere in the Twitter story — the gradual tightening, the shifting terms, the unilateral decisions that developers had no recourse against.
The data and antitrust dimension is where platform power became a matter of law, and APIs were at the center. The FTC’s antitrust lawsuit against Facebook, which I wrote about in 2020, put APIs squarely in the frame — the argument that Facebook had used API access strategically to consolidate market power, granting access to allies and cutting it off from potential competitors. This is platform power as anticompetitive weapon: the API as the mechanism through which a dominant platform entrenches its dominance, deciding who gets to build on it and who gets foreclosed. The platform’s control over its API is control over a piece of the market, and when the platform is dominant enough, that control becomes a matter of antitrust and public policy. The politics of platforms reached the courts because the power platforms wield through their APIs became too consequential to leave ungoverned.
The visibility-and-control insight is the sharpest articulation of platform politics I’ve reached recently, and it cuts to the core. I wrote in 2025 that API visibility and control is at odds with power and control — meaning that the transparency and accountability that would constrain platform power are precisely what platforms resist, because their power depends on opacity and unilateral control. A platform that was fully transparent about how it grants and revokes access, that gave developers genuine recourse, that couldn’t unilaterally change the terms, would be a platform with less power. The political struggle around platforms is fundamentally about whether their power will be visible and accountable or opaque and unconstrained. This is why the federated alternatives matter so much to me: Mastodon and the federated protocols I’ve championed represent a fundamentally different platform politics, where no single party holds the power, where the protocol is owned by no one, and where the ability to participate can’t be revoked by a corporate decision. The federated model is the political alternative to platform power — distributing the control that platforms concentrate.
The deepest political truth about platforms is that they represent a concentration of power that the API both enables and could constrain. APIs gave platforms their power — the technical means to mediate, control, and extract at scale. But APIs could also, in principle, constrain that power — through transparency, through portability, through federated architectures, through regulation that mandates fair access. The politics of platforms is the ongoing struggle between the platforms’ interest in concentrated, opaque, unilateral control and the public interest in distributed, transparent, accountable power. I’ve watched platforms rise on the openness of their APIs and then use those same APIs to enclose and extract, and I’ve come to see the platform as the defining political-economic structure of the API age — the place where the power dynamics of the digital economy are most concentrated and most consequential. Whether that power is held accountable or left unconstrained is one of the central political questions of our time, and the API is the terrain on which that question gets contested. The platform is where APIs become power, and the politics of APIs is, at its core, the politics of platform power.
References
- Open vs Closed APIs
- Tension Between API Owners And Consumers
- APIs Used To Close Rather Than Open The Internet
- The Subtle Ways In Which Power Asserts Itself In Face Of API Engagements
- The Many Meanings Of Do Not Make The Same Mistake As Twitter Did With Their API
- The Many Ways In Which APIs Are Taken Away
- APIs Are At The Center Of The Federal Trade Commission (FTC) Lawsuit Against Facebook
- Mastodon Opening The Age Of Federated APIs
- Twitter Is The Most Important API
- API Visibility And Control Is At Odds With Power And Control
