What is an API — in plain words, and why you ping a hundred of them daily

Here's a surprising thing: you use dozens of other people's programs without ever stepping inside them. A weather app doesn't compute the weather itself — it asks someone else's server. The "sign in with Google" button doesn't know your password — it asks Google. All of this happens through one thing called an API. Once you feel it, half the "magic" in apps stops being magic.

What it is in one line

An API is the window through which one program asks another to do something or hand over data. You don't barge into someone's kitchen — you walk up to the window, say what you need, and get a finished answer back.

The classic analogy is a café menu. You don't go to the stove and teach the cook. You look at the menu (the list of what you're even allowed to ask for), name a dish, and a plate comes out. An API is exactly that menu for programs: the list of requests a service will accept, and the format of the answer it returns.

The acronym (you won't need it, but here it is): Application Programming Interface — a way for one program to talk to another.

How it works, step by step

Every API call is a short dialogue: your program sends a request, the other server sends a response.

1. Your code builds a request. It has an address — where you're knocking (called an endpoint, e.g. api.weather.com/now?city=London) and what you're asking for.
2. The request flies to the other server over the internet, using plain HTTP — the same protocol that loads websites in your browser.
3. The server does the work — looks in its database, computes, checks — and builds an answer.
4. The answer comes back — almost always as JSON: tidy text like {"temp": 17, "wind": 4} that your program parses easily.

The trick is you don't need to know how the server computed the weather. All that matters is the menu (what to ask) and the plate's shape (what comes back). That's the power of an API: you reuse someone's hard work without diving into it.

Why it matters to you

The moment you build anything real, you build it out of other people's APIs, like LEGO. Need a map in your app — grab a maps API. Need to send an email — an email API. Want your bot to reply like a human — call a language-model API. You don't write everything from scratch — you wire ready-made windows together.

So the first real skill of a vibe-coder isn't "write an algorithm" — it's read someone's docs and connect. Which address, which key, what comes back. Sounds boring, but that's exactly what turns an idea into a working thing in an evening. When you get to practice, see the step-by-step guide on how to connect an API to your project.

One more thing: almost every useful API is locked behind a key. The key is your pass to the window — it counts how much you've requested and sometimes charges money. So you can't leave it exposed in your code — but that's another story.

How an API differs from a webhook

They're easy to confuse, but the direction is opposite. An API is you going to a service and asking. A webhook is the service coming to you to report that an event happened. API — you call the café and order. Webhook — the café calls you: "order's ready." They often work as a pair.

Where you'll meet an API first

Most likely when you want to add to your project something you'd rather not write by hand: payments, maps, sending messages, an answer from an AI. Good news — for practice there's a pile of free APIs with no payment and no painful sign-up. Start there: wire in weather or currency rates and you instantly see how the bricks click into an app.

FAQ: Is an API a website or a program?

Neither. It's an interface — a set of rules and addresses you use to reach a program. A website's interface is for humans (buttons, images); an API's interface is for other programs (requests and JSON responses). The same service often has both: a site for people and an API for programs.

FAQ: Do I need to know programming to use an API?

A little. The call itself is a couple of lines of code, or even one terminal command. These days an AI agent often writes even those: you say "connect this weather API," it builds the request. But understanding what an endpoint, a key, and a JSON response are still helps — otherwise you won't know what to fix when it breaks.