Why Companies Open Their Doors

Running a public API costs real money. Servers that answer day and night, documentation kept current, a support team reading partner emails — none of it is free. So before this book teaches you to walk through these doors, one honest question deserves an answer: why do companies build the doors at all?

Because an API turns a product into a platform. Other people's software starts bringing you customers, data, and revenue that you could never have built alone. The door is not generosity. It is strategy — and knowing that explains everything about how the door is guarded.

Integrations Sell the Product

Riverport's official transport app shows Tandem bikes right next to the buses and trams. Tandem did not build that app — the city did, using Tandem's API. Every rider who discovers a bike through it is a customer Tandem acquired without spending anything. That arrangement has a name: an integration — one product connected into another through an API. Every integration is free distribution, which is why companies chase them.

Partners Build What You Will Not

The tourism board wanted a "bike your visit" trip planner for tourists. Tandem was never going to build one — too niche, wrong business. But the API was there, so the tourism board built it themselves, and now Tandem gets tourist rides from software it never paid for. Multiply that by every partner with an idea, and the API becomes a workforce: hundreds of products Tandem's own team will never have to write.

Sometimes the API Is the Whole Product

The payment provider from two pages ago has no product you can hold. No app to browse, no site worth visiting — the API is the product. Companies pay to use it, metered like electricity: so much per thousand requests, so much per payment processed. Map providers work this way. So do the AI companies whose models answer through an API — you will meet one properly in the last chapter. For these businesses, the counter is not a side door to the shop. The counter is the shop. (You will also hear "API-first" at work — usually meaning the API gets designed before the apps that use it; the phrase is looser than the idea.)

A Product Has Rules

Now the practical consequence, and the bridge to everything ahead. Because an API has users, costs, and revenue, it has rules: sign up first, carry a key, stay within your quota, follow the terms. The doorkeeping you are about to spend two chapters learning — keys in Chapter 5, documentation in Chapter 6, request limits in Chapter 8 — is not bureaucracy for its own sake. It is what a business puts around a door it paid to build. Once you see the business model, the paperwork reads as exactly what it is: the terms of a deal, and usually a fair one.