What Is an API? A Plain-English Guide With Real Examples

Editorial disclosure: Recribel is an independent, reader-supported tech publication. If you buy software or services through links on this site, we may earn an affiliate commission at no extra cost to you.

By Aryu for Recribel. Updated October 27, 2026. About 10 minutes to read.

The short answer

An API (Application Programming Interface) is a set of rules that lets one piece of software ask another piece of software to do something, and get an answer back, without either one needing to know how the other works inside.

  • You never see APIs, but every login, payment, map and weather widget uses one.
  • An API call is a request (what you want) and a response (what you get back).
  • Most web APIs send data as JSON over HTTP, the same protocol your browser uses.

Open any food delivery app and watch what happens. The map shows your rider moving, the payment goes through in a few seconds, and the app texts you an update. None of those features were built from scratch inside that app. They were borrowed from other services, and the thing that makes the borrowing possible is an API.

This guide explains what an API is in plain language, lets you send a pretend request and watch it travel, and gives you a way to try a real one in under a minute. Think of it as a trail with seven stops. Each stop ends with a checkpoint and a badge, and by the finish line you will have walked from “what is this?” to “I just called one.”

Stop 1 of 7

What is an API?

Think of a restaurant. You sit at a table and you do not walk into the kitchen to cook your own food. Instead you tell the waiter what you want, the waiter carries the order to the kitchen, and later the waiter brings the dish back to you.

An API plays the role of that waiter. Your app is the customer, the other service is the kitchen, and the API is the agreed way of placing an order and receiving the result. The kitchen can change its recipes, its stoves and its staff, and as long as the menu stays the same, you never notice.

Your app

The customer. It decides what it wants and asks for it.

The API

The waiter. It carries the order and brings the answer back.

The other service

The kitchen. It does the real work behind the scenes.

That last point is the real value of an API.

It is a contract: “send me a request shaped like this, and I will send you back a response shaped like that.”

Both sides can change everything behind the scenes as long as they keep the contract.

Checkpoint

An API is a contract: you ask in an agreed format and get an answer in an agreed format.

Badge unlocked: API basics
Stop 2 of 7

How does an API work?

Before any of this happens, your device first has to find the server’s address, which is the job of DNS. If that part is new to you, How DNS Works: What Happens Before a Website Loads explains it in plain English. Once the address is known, almost every web API follows the same four-step conversation:

  1. The client sends a request. It names what it wants (an address called an endpoint) and what it wants to do with it (a method such as GET or POST).
  2. The server checks the request. It confirms who is asking (often with an API key or token) and whether the request is allowed and well formed.
  3. The server does the work. It reads from a database, runs a calculation or calls yet another service.
  4. The server sends a response. It includes a status code that says how things went and, usually, data in JSON format.

Send a request and watch it travel

This is a simulation using a made-up book service. Pick a scenario, press send, and follow the glowing dot.

Your app API Server
Pick a scenario above, then press send.

What a real request and response look like

Here is an illustrative example. The address is made up, but the shape is typical of real APIs. The request asks a book service for books by one author:

GET https://api.example.com/v1/books?author=austen
Authorization: Bearer YOUR_API_KEY

And the response might come back like this:

200 OK

{
  "results": [
    { "id": 101, "title": "Emma", "year": 1815 },
    { "id": 102, "title": "Persuasion", "year": 1817 }
  ]
}

The 200 OK line is the status code, and the block below it is JSON, a simple text format that both humans and programs can read. Your app takes that JSON and turns it into whatever you see on screen.

The parts of an API request at a glance

Endpoint

The address of the thing you are asking about.

For example: /v1/books
Method

The action: read, create, update or delete.

For example: GET, POST, PUT, DELETE
Parameters

Details that narrow down the request.

For example: ?author=austen
Headers

Extra information such as your key and data format.

For example: Authorization
Body

The data you send when creating or updating something.

For example: a JSON object
Checkpoint

Every API call is a request going out and a response coming back, with a status code and usually JSON.

Badge unlocked: Request tracker
Stop 3 of 7

Real-world examples of APIs you use every day

You have probably used dozens of APIs today without noticing. A few common ones:

Illustration of a folded map with a route and a location pinMaps inside other apps. Delivery and ride apps usually do not draw their own maps. They ask a mapping service for routes and locations through its API.
Illustration of a payment card and a phone showing a success tickOnline payments. When a shop’s checkout page charges your card or UPI app, it talks to a payment provider’s API instead of handling the money itself.
Illustration of a key unlocking a sign-in window“Sign in with Google.” The website asks Google to confirm who you are, and Google answers without ever handing over your password.
Illustration of a sun peeking out from behind a cloudWeather widgets. Your phone’s home screen asks a weather service for the forecast at your location and displays the reply.
Illustration of a chat bubble with sparklesAI features in apps. Many apps with a built-in assistant send your question to an AI provider’s API and show the answer that comes back.

Curious how AI agents put APIs to work? AI Agents Explained in Plain English: What They Do and Where They Fail covers what they can do and where they fall short.

Checkpoint

Maps, payments, logins, weather and AI features all run on APIs you already use.

Badge unlocked: Everyday API spotter
Stop 4 of 7

What are the different types of APIs?

APIs get grouped in two useful ways: by who can use them, and by the style they follow.

By access

  • Public (open) APIs are available to any developer, usually with a free sign-up.
  • Partner APIs are shared with specific business partners.
  • Private (internal) APIs connect the parts of a single company’s own systems.

By style

  • REST is the most common web style. It uses ordinary web addresses and methods like GET and POST, and usually returns JSON.
  • GraphQL lets the client describe exactly which fields it wants in a single request, which can reduce wasted data.
  • WebSockets keep a connection open so data can flow both ways in real time, which suits chat apps and live scores.

If you are just starting out, REST is the one to learn first, because most of the APIs you will meet follow it.

Checkpoint

Start with REST, and remember that APIs can be public, partner or private.

Badge unlocked: API type guide
Stop 5 of 7

What do API status codes mean?

Every response includes a three-digit status code. You do not need to memorize them all, but these show up constantly. Tap any card to see what it means.

200 OK

The request worked.

201 Created

A new item was made successfully.

400 Bad request

The request was malformed or missing something.

401 Unauthorized

The key or token is missing or invalid.

403 Forbidden

You are known, but not allowed to do this.

404 Not found

The endpoint or item does not exist.

429 Too many requests

You hit the provider’s rate limit, so slow down.

500 Server error

The problem is on the provider’s side.

A handy rule: codes starting with 2 mean success, codes starting with 4 mean something was wrong with the request, and codes starting with 5 mean the server had trouble. For the full list, the MDN Web Docs page on HTTP status codes is a reliable reference.

Quick check

You send a request without an API key. Which status code are you most likely to get back?

Keep API keys private. An API key works like a password for your app. Do not paste it into public code, screenshots or a website’s front-end code, where anyone can read it. If a key is ever exposed, most providers let you revoke it and create a new one. For a recent reminder of why web security basics matter, see PHP2Shell Explained.

Checkpoint

2xx means success, 4xx means check your request, and 5xx means the server had trouble.

Badge unlocked: Status code decoder
Stop 6 of 7

How can I try an API myself?

You can make a real API call right now with nothing installed. JSONPlaceholder is a free practice API built for learning, and it needs no key. Open any web page, press F12 to open the browser’s developer tools, switch to the Console tab, and run this:

fetch("https://jsonplaceholder.typicode.com/posts/1")
  .then(response => response.json())
  .then(data => console.log(data));

The browser sends a GET request, the server replies with JSON, and the console prints it as an object you can expand. That is the whole idea of an API in three lines. From here you can change the number at the end of the address, or try adding /comments to see a different kind of data.

What you will see

An object with fields such as userId, id, title and body, which is the response from the server printed in your console.

Checkpoint

A real API call is just a request from your browser and a JSON reply.

Badge unlocked: API explorer
Stop 7 of 7

Frequently asked questions

What does API stand for?

API stands for Application Programming Interface. “Interface” is the key word: it is the point where two programs meet and exchange information.

Is an API the same as a website?

No. A website is built for people to read and click, while an API is built for programs. A website returns pages with design and layout. An API returns raw data, usually JSON, that another program can use however it likes.

Do I need to know how to code to use an API?

To build with APIs, some coding helps. But many no-code tools let you connect services through their APIs using forms and buttons, and testing tools let you send requests without writing a program.

Are APIs free?

Some are, some are not. Many providers offer a free tier with a limit on how many requests you can make, then charge for heavier use. Always read a provider’s pricing and rate limit page before building something that depends on it.

What is the difference between an API and an SDK?

An API is the set of rules for talking to a service. An SDK (software development kit) is a toolbox of ready-made code, libraries and documentation that makes using that API easier in a particular programming language.

Checkpoint

You now have the basics, the vocabulary and a place to practice.

Badge unlocked: API navigator
Finish line

The bottom line

An API is a contract between two programs: ask in the agreed format, get an answer in the agreed format. That single idea is why apps can share maps, payments, logins and AI without rebuilding any of them, and once you can read a request and its response, most of the modern web becomes much easier to understand.

API basics
Request tracker
Everyday API spotter
API type guide
Status code decoder
API explorer
API navigator

That is the whole trail. Thanks for walking it with Recribel.

Keep reading on Recribel

You can also browse every Spotlight or catch up with the Daily pulse.