What Is an API

Every app you use talks to other apps behind the scenes. Your weather app fetches temperature from a weather service. Your food delivery app checks restaurant menus from a restaurant database. The tool that makes all this communication possible is called an API.

What Is an API?

API stands for Application Programming Interface. Think of it as a waiter at a restaurant.

You (the customer) sit at the table. The kitchen prepares food. You never walk into the kitchen yourself. Instead, the waiter takes your order, goes to the kitchen, and brings your food back to you.

[ You ]  ──── order ────▶  [ Waiter ]  ──── request ────▶  [ Kitchen ]
[ You ]  ◀─── food  ────  [ Waiter ]  ◀─── response ────  [ Kitchen ]

In software terms:

  • You = the app or website (called the client)
  • Waiter = the API
  • Kitchen = the server that holds the data or logic

A Real Example: Booking a Flight

When you search for flights on a travel website, the site does not store all flight data itself. It sends a request to an airline API, which responds with available flights, prices, and times. The website just displays what the API returns.

Travel Website ──▶ API Request: "Flights from Delhi to Mumbai on June 10"
                         ▼
                   Airline Server
                         ▼
API Response: [ Flight AI202, 6:00 AM, ₹4,500 ]
              [ Flight 6E101, 9:30 AM, ₹3,800 ]
Travel Website shows these results to you

What Makes an API a REST API?

There are many types of APIs. REST (Representational State Transfer) is the most popular style used on the web today. A REST API uses standard web technology — specifically HTTP — to send and receive data. It is simple, readable, and works across any programming language or platform.

You do not need special software to use a REST API. A browser, a mobile app, or a command-line tool can all talk to a REST API using the same rules.

Why Does REST API Design Matter?

Building an API is easy. Building a good API takes thought and planning.

A poorly designed API frustrates developers who use it. URLs are confusing, error messages are unclear, and behavior is unpredictable. A well-designed API is a joy to work with — it is predictable, consistent, and self-explanatory.

Companies like Google, Twitter, Stripe, and GitHub invest heavily in API design because their APIs are used by millions of developers. A great API can make or break a product.

Who Uses APIs?

  • Mobile apps – an Android or iOS app fetches data from a server API
  • Web browsers – a React or Angular frontend calls a backend API
  • Other servers – microservices communicate with each other through APIs
  • Third-party integrations – payment gateways, maps, and SMS services expose APIs for other apps to use

The API Conversation Model

Every API interaction has two sides: a request and a response.

CLIENT                        SERVER
  │                              │
  │── Request ──────────────────▶│
  │   (What do you want?)        │
  │                              │ (processes the request)
  │◀── Response ─────────────────│
  │   (Here is what you asked)   │

The client always starts the conversation. The server always responds. This one-direction initiation is a key characteristic of REST.

Key Points

  • An API is a messenger that connects two software systems
  • REST is the most widely used API style on the modern web
  • Every REST API interaction consists of a request from the client and a response from the server
  • Good API design saves time, reduces confusion, and makes software easier to build
Back to courses
Next lessons

Leave a Comment