Antitrust is where the politics of APIs collides with the reality of platform power, and it’s a theme I’ve tracked from the earliest days of watching platforms use their APIs as competitive weapons. APIs are supposed to enable an ecosystem — to let third-party developers build on a platform and create value together. But platforms have repeatedly shown that the same API that invites developers in can be weaponized against them: the platform opens an API to attract an ecosystem, lets developers build dependent businesses, and then changes the terms, restricts access, or shuts the API down entirely once those developers become competitive threats or once the platform decides it wants the value for itself. This bait-and-switch is one of the most important political dynamics in the API economy, and it’s increasingly drawing the attention of antitrust regulators who recognize that control over API access is control over competition itself.
The power asymmetry between platforms and developers is the foundation of the problem, and I named it early. I wrote in 2012 about the inherent tension between API owners and consumers — the structural imbalance where the platform holds all the power and the developers who build on it have almost none. A developer who builds a business on a platform’s API is utterly dependent on that platform’s continued goodwill, and the platform can change the rules, raise the prices, restrict the access, or pull the plug at any time. This isn’t a partnership of equals; it’s a relationship where one party has total control and the other has total dependence. The Instagram case I wrote about in 2012 — what happens to Instagram API developers after the Facebook acquisition — captured the vulnerability perfectly: developers who built on Instagram’s API found their fate suddenly in the hands of an acquirer with its own agenda. The asymmetry is the precondition for the abuse, and the abuse is what antitrust is increasingly concerned with.
The history of platforms weaponizing API access is long, and I documented it as it happened. Twitter’s progressive restriction of its API — cutting off the firehose, restricting third-party clients, and ultimately strangling the ecosystem it had once cultivated — is the canonical example, and I covered the PeopleBrowsr injunction fight as an early sign that platforms shutting off API access could destroy dependent businesses. I argued in 2015 that a platform’s secret sauce does not include restricting access to its APIs — pushing back on the idea that gatekeeping API access is a legitimate competitive strategy rather than an anticompetitive one. The pattern repeated across platforms: cultivate an ecosystem, let developers build, then restrict or shut down access once the platform’s interests shifted. This is API access as a competitive weapon, and the developers who built in good faith on the platform’s invitation are the ones who pay the price when the platform decides to wield it.
The copyright dimension is where API control became a formal legal battle over competition, and I was deeply engaged with it. The Oracle v. Google case — over whether APIs themselves can be copyrighted — was fundamentally an antitrust-adjacent fight about whether a company could use copyright to lock down the API infrastructure that enables competition and interoperability. I wrote about the case heading to the Supreme Court and signed onto amicus efforts with the EFF, because the stakes were enormous: if APIs are copyrightable and their reimplementation can be blocked, then platforms gain a powerful new legal tool to prevent competitors from building compatible systems. API copyrightability would turn APIs from enablers of interoperability into instruments of lock-in and competitive exclusion. The fight over API copyright was, at its core, a fight about whether the openness that makes APIs valuable for competition would survive, or whether they’d become another mechanism for entrenching platform dominance.
The regulatory turn is the most significant recent development, and it’s where antitrust is finally confronting platform power directly. I wrote in 2020 about how APIs are at the center of the FTC’s antitrust lawsuit against Facebook — because the FTC’s case alleged that Facebook used API access as an anticompetitive weapon, cutting off competitors from the platform APIs they depended on. This was a landmark: a major antitrust action in which the weaponization of API access was central to the government’s theory of monopolistic conduct. It validated what I’d been arguing for years — that controlling API access is controlling competition, and that platforms wielding that control to crush rivals is an antitrust problem. The Twitter and Reddit API shutdowns of 2023, which I called the canaries in the public API coal mine, signaled that this dynamic was intensifying: platforms restricting and monetizing API access in ways that harm the developers and the public who depend on them, raising exactly the questions about platform power that antitrust exists to address.
Where I land on antitrust is that API access has become one of the central battlegrounds of platform power, and that the regulatory and legal systems are finally beginning to recognize it. The power asymmetry between platforms and developers, the long history of platforms weaponizing API access against the ecosystems they cultivated, the copyright fights over whether APIs can be locked down, and the antitrust actions confronting platforms for using API control anticompetitively all point to a single recognition: control over APIs is control over competition, interoperability, and innovation itself. Interoperability — mandated, protected API access — is increasingly discussed as an antitrust remedy precisely because forcing platforms to maintain open, fair API access is one of the most direct ways to constrain their monopoly power. The deepest political point is that APIs are infrastructure for competition, and when a handful of dominant platforms control that infrastructure and wield it to entrench their dominance, the openness that makes APIs valuable gets turned against the very ecosystem it was supposed to enable. Antitrust is the political and legal system catching up to a dynamic the API community has lived for over a decade — and getting the rules right, so that API access serves competition rather than monopoly, is one of the most consequential fights in the entire politics of APIs.
References
- What Happens To Instagram API Developers After Facebook Acquisition
- Tension Between API Owners And Consumers
- PeopleBrowsr Wins Temporary Injunction To Keep Twitter From Shutting Off Firehose
- Politics Of APIs
- Your Secret Sauce Does Not Include Restricting Access To Your APIs
- API Copyright Heading To The Supreme Court
- APIs Are At The Center Of The Federal Trade Commission (FTC) Lawsuit Against Facebook
- Twitter And Reddit APIs Are Canaries In The Public API Coal Mine
