What is an API? A Simple Explanation with Real Examples

You've heard the word API everywhere. In job descriptions, in tutorials, in tech Twitter. But what actually is it?

The waiter analogy

Think of an API like a waiter at a restaurant.

You (the app) don't walk into the kitchen (the server) yourself. You tell the waiter what you want. The waiter goes to the kitchen, gets your food, and brings it back.

That waiter is the API.

A real example you use every day

When you open Zomato and it shows a map of nearby restaurants — that map comes from Google Maps. Zomato didn't build its own maps. It asked Google's Maps API: "Give me a map for this location." Google sent it back. Zomato displayed it.

You use APIs dozens of times a day without knowing it.

Another example — weather apps

Your phone's weather app doesn't have its own satellites. It calls a weather API, asks "what's the weather in Bangalore right now?", and displays whatever comes back.

What does an API actually look like?

Here's a real API call in Python — just 3 lines:

import requests
response = requests.get("https://api.open-meteo.com/v1/forecast?latitude=12.97&longitude=77.59&current_weather=true")
print(response.json())

Run this and you get live weather data for Bangalore returned as text your program can read. That's an API call.

Why developers love APIs

• You don't rebuild what already exists
• Google Maps, payments, weather, SMS — all available as APIs
• You focus on your app, APIs handle the hard parts

The one-line summary

An API is a messenger that lets two apps talk to each other — you send a request, it sends back data.

That's it. Next time someone says "we integrated an API" — you know exactly what happened.

---

Written by Raaga Priya Madhan — CSE student, Bangalore. I write about CS concepts simply. Connect with me on LinkedIn