Why this matters — even if you never write a line of code
Here's something most people don't realise: the apps you use every day aren't self-contained. Your weather app doesn't have its own weather stations. Spotify's "share to Instagram" button wasn't built by Spotify. The "Pay with PayPal" button on a shop's website wasn't built by the shop.
All of these things work because apps talk to each other. And the language they use to do that talking? That's an API.
Understanding APIs isn't just for developers. No-code tools like Zapier and Make are built entirely around connecting APIs — they're just a friendlier face on the same idea. AI tools like Claude and ChatGPT are available via API, which means anyone can wire them into their own apps and workflows. The concept unlocks a lot. This is where to start.
APIs are the connective tissue of the modern internet. Almost nothing you use online works in isolation — it works because it's talking to something else through an API. Once you see this, you see it everywhere.
The waiter who doesn't cook
Here's an analogy that makes this click instantly.
Imagine you're at a restaurant. You're hungry, but you're not going into the kitchen yourself — you don't know how the equipment works back there, and frankly it's not your job.
So you tell the waiter what you want. The waiter walks to the kitchen, places your order, waits for the food to be prepared, and brings it back to your table. You never saw the inside of the kitchen. You never needed to.
The waiter is the API. You are the app making a request. The kitchen is the service being asked — a weather database, a payment processor, a mapping system. The food is the response that comes back.
That's genuinely what an API is. The formal definition: an API (Application Programming Interface) is a set of rules that lets one piece of software ask another piece of software to do something — without either side needing to know how the other works internally.
The word interface is the key part. An interface is a surface you interact with — like the buttons on a TV remote. You press volume up without knowing anything about the electronics inside. The remote is the interface to the TV. An API is the interface between two pieces of software: a defined surface that says "here's what you can ask for, here's how to ask for it, and here's what you'll get back."
An API is a contract between two systems. It says: "ask for this, in this format, and I'll give you that back." Neither side needs to understand the other's internals — just the surface between them. This is what makes the modern internet composable: apps can be built on top of other apps without either team ever meeting.
Every API conversation has three parts
When one app talks to another through an API, the exchange always follows the same pattern. Think of it like a very structured phone call — there's always a question, a specific number to call, and an answer that comes back.
The Request
What you're asking for. "Give me the current weather in London." The request is sent by whoever — or whatever — wants the information. Your phone, your browser, another app.
The Response
What comes back. Usually data — a temperature reading, a list of songs, a payment confirmation. The response is exactly what the other service returns after handling your request.
The Endpoint
The specific address you send the request to. Think of it like a specific dish on a menu — each endpoint does one particular thing. Example: api.weather.com/current
Your app never sees the service's internals — just the data it asked for.
Notice that the request travels out and the response travels back — your app is never directly touching the weather database, the bank's systems, or Google's servers. It's talking to an API that sits in between, handling all of that on your behalf. Exactly like the waiter.
APIs you've already used today
Once you know what to look for, you'll notice APIs everywhere. Here are five you've almost certainly encountered — probably in the last 24 hours.
Most APIs aren't open for anyone to call without limits. They require an API key — a private token that proves you're authorised to use the service, and that usage can be tracked and billed. Exposing an API key publicly (say, in code you share on GitHub) can result in unexpected charges or your account being misused. This is one of the most important things to understand about working with APIs — and it's covered in full in the companion guide: API Authentication — Keys, OAuth & Beyond.
Quick reference
Four terms worth keeping in your vocabulary from here on: