APIs · Lesson 1 of 6
What an API actually is
Explain what an API is without jargon, and recognise that you already use them daily.
An API is how one program asks another program for something.
That is genuinely it. When a food app shows you a map, it did not build a mapping system — it asked a mapping service, over the internet, and got an answer back. When your bank app shows a balance, it asked the bank's servers.
The useful mental picture is a waiter in a restaurant. You do not walk into the kitchen. You give the waiter an order in a format they accept, they bring back food. You never see how the kitchen works, and you do not need to. The API is the waiter: a defined way to ask, and a defined shape of answer.
Why this matters for automation. Until now your Python programs only worked with information you typed into them. An API is how a program gets real information from the outside world and makes real things happen in other systems — read today's exchange rate, send a WhatsApp message, add a row to a sheet, create a lead in a CRM.
The vocabulary you need, and no more:
Request — you asking. Response — what comes back. Endpoint — the specific address you ask, like a specific dish on the menu. JSON — the format the answer usually arrives in.
Two things beginners find surprising:
APIs are just web addresses. You can open many of them in a browser and see the raw answer. It is not a separate mysterious technology.
And an API is a promise, not a favour. The provider has documented what it accepts and what it returns, and other people's software depends on that staying stable. This is why reading documentation is the actual skill, which is the next lesson.
Open this in your browser: https://api.github.com/users/octocat — you have just made an API request. Read the answer. Find the fields for the account name and the number of public repositories.
Check what you learned
Create your free BvLogic ID to take the quiz and record your score.
Create your BvLogic ID