What an API actually is and why you care.

Getting Started · 5 min read

I've explained APIs to three different clients in three completely different ways. And every time, the moment it clicks, you can see it on their face. The term sounds intimidating. It's not. An API is just a way for your app to talk to someone else's system. It gets data, it sends data, and it does it in a structured, predictable way.

The reason you care is simple. Your app almost certainly needs at least one. And the cost of integrating with an API is something your developer will need to factor into the build. So it helps to understand what you're paying for.

Three explanations that worked

For a client in construction, I explained it like calling ahead to a supplier. Before you drive across town, you ring up and ask what stock they have. The supplier checks their system and gives you an answer. Your app does the same thing, but digitally. It asks another system a question, gets an answer, and uses that answer to show the user something useful. That's an API call.

For a client building a vehicle management app, it was more concrete. Their app needed to pull real vehicle data using a number plate. Type in the rego, hit search, and the app comes back with the make, model, year, and registration status. That data doesn't live in our app. It lives in a government system. The API is the connection between the two. It asks the roads authority, "What do you know about this plate?" and brings back the answer.

For a client building a messaging platform, a developer on the call described it perfectly: "It's a tunnel between two businesses with security guards at each end." Both sides agree on what data can pass through, how it's formatted, and who's allowed to request it. That's the API contract. If either side changes the rules without telling the other, the tunnel breaks.

Why it matters for your budget

APIs aren't free. Some are open and publicly available. Others charge per request. Others require a commercial agreement before you can access them. And even the free ones take development time to integrate. Your developer has to read the documentation, build the connection, handle errors when the other system is down, and test that everything works reliably.

The number of API integrations your app needs directly affects your development cost and timeline. An app that only talks to its own database is simpler. An app that pulls data from three external systems, sends notifications through a messaging service, and processes payments through a payment gateway has five integration points. Each one adds complexity, and complexity costs money.

Gartner calls APIs the "connective tissue" of the digital economy. That's accurate. Almost every modern app relies on APIs to do things it can't do alone. Your app doesn't need to store every piece of data or build every feature from scratch. It just needs to know where to ask.

What to ask your developer

When you're planning your app, ask which features require external APIs. Then ask what happens when those APIs change or go down. A good developer will build in fallbacks and error handling. A less experienced one might not think about it until it breaks in production.

You don't need to understand the technical details. You just need to know that your app talks to other systems, that those connections cost time and money to build, and that they need to be maintained over time. APIs change. The external service might update their rules, deprecate a feature, or start charging differently. That's ongoing work, not a one-time build.

So when your developer quotes you and there's a line item for "API integration," now you know what it means. It's the tunnel. It's the phone call to the supplier. It's the connection that makes your app useful beyond its own walls.

Sources
Application Programming Interface (Gartner) - APIs are the "connective tissue" of the digital economy, enabling apps to exchange data with external systems.

Related blog posts:

The difference between a designer and a developer →

You don't need a technical co-founder →

What happens between the prototype and the App Store →