Welcome

What This Project Is About

If you have ever wondered — or wanted a simple way to learn about — some of the magic that makes up the functionality of a webpage or online software, this site was made for you.

API calls happen in order to make webpages and online software function the way that they do. Roughly 80–95% of mobile app traffic and 70–83% of web traffic is API calls. This is a guided tour of the messages that run the internet — start from wherever you are now.

Here's what's inside:

  • API Basics explains what a call is, the one request-and-response pattern every call follows, and how calls travel across the internet.
  • Types of API Calls walks through the eight main types — when each came out, why it was invented, and a real request and response for each.
  • Who Makes an API Call lists the seven kinds of callers — browsers, phone apps, servers, smart devices and more — with an example of each.
  • Options for Making API Calls shows ten ways a call gets sent, from no-code tools to a few lines of code.
  • How Software Companies Use API Calls shows what goes out behind the products you already use.
  • Make an API Call is a safe practice page where you build and send one yourself.
  • Building a Custom API Integration teaches you to read a company's API documentation and plan a connection of your own.
  • API Call Quiz closes the loop with ten questions on the facts everyone should know, each hiding an answer you reveal yourself.

You don't need to

  • know how to program
  • install anything or create any accounts
  • already know what a server is
  • read documentation written for engineers

If you can use a web browser, you can use every page here.

Who it's for

Beginner to intermediate. Concepts are broken down simply first, then shown as a real example you can read.

A Simple Example

How an API call works from your browser to a company server, step by step

1You choose something

You pick a tab, a filter or a button on a webpage.

2Your browser sends a request

An API call goes out to the company's server asking for what it needs.

3The server does the work

It looks the data up, or carries out the action that was asked for.

4The answer comes back

That's the response — the data you asked for, or the result of the action.

5You see it on the page

Your browser puts the answer on your screen, usually in a fraction of a second.

Where the Call Goes

An API call doesn't only run between your browser and one company's server. There are three routes you'll meet on this site — and one feature usually uses all three at once.

Your browser → a company's server

You search for “developers in Europe who love hiking”. Your browser sends that question to DuckBuddy's server, and DuckBuddy's server sends the matching profiles back for the page to show you.

One company's server → another of its own servers

DuckBuddy's main server quietly asks its own matching server, “How well do Anna and Sofia fit?” and gets back 94%. It happens inside the company's own network, so you never see this one happen.

Company A's server → Company B's server

You click Go Premium for $9.99. DuckBuddy's server asks the payment company's server to charge the card, the payment company replies “approved”, and DuckBuddy unlocks the Agent.

Who This is For

Beginner to intermediate. Every concept is broken down into simple pieces first — what a call is, what's inside one, what the answer looks like — and then shown as a real example you can read: the request that goes out, the response that comes back, and why it's built that way.

Nothing here assumes you already know the vocabulary. Words like endpoint, method and authorization are explained the moment they show up, anything that looks like code is walked through in ordinary English, and the deeper detail sits behind buttons you can open or ignore.

Three places to start, depending on how much you already know. Any of them is a fine front door.

Level 1Brand new to this

You've heard the word API and would like to know what people mean when they say it. No assumed knowledge — every term is explained the first time it appears.

Start with: API Basics

Level 2Getting the picture

You already know that a request goes out and an answer comes back, but the names — REST, GraphQL, webhooks, WebSockets — all blur together. The timeline and the eight examples pull them apart.

Start with: the timeline on Types of API Calls

Level 3Ready to try it

You want to send a call yourself and understand what you're looking at. The practice page lets you build one against a simulated company, with no account, no installation and nothing to break.

Start with: Make an API Call

The Main Sections

Eight pages, each standing on its own. Click a card to open it, then follow the link inside to go to that page.

A Suggested Path

If you'd rather be told where to go first: this order takes a complete beginner to the point where they can send a call and read the answer. Skip around freely — no page depends on another.

Six Steps, Beginner to Intermediate

  1. API Basics

    Learn the single pattern behind every call, what's inside one, and how it travels across the internet.

  2. Types of API Calls

    Meet the eight types in the order they were invented and why each one was needed, with a request and a response for each.

  3. Options for Making API Calls

    See the twelve ways a call can actually be sent, and which of them belongs to you rather than to a developer.

  4. How Software Companies Use API Calls

    Spot the same pattern behind products you already use, so the idea stops being abstract.

  5. Make an API Call

    Send one yourself in a simulator — pick a company, choose a method and endpoint, add authorization, read the reply.

  6. Building a Custom API Integration

    Read a real API's documentation and work out what your own connection would need.

  7. API Call Quiz

    Finish by testing yourself: ten questions on the facts that matter, with an answer to reveal under each one.

By the end you'll have seen each type, sent one yourself, and read a real API's documentation.

How to Use These Pages

Short explanation first, detail behind a click second.

Every page works the same way: a simple explanation up front, then the extra detail you can open only if you want it. Buttons like When It Came Out, Why use it and Where it travels are all clickable — nothing is hidden, and nothing is required reading.

There is a quiz at the end — the API Call Quiz — but it isn't there to grade you. It's to help you see what you learned after going through this explorer course. Read the pages in order, jump to whichever one matches the question in front of you, or treat the practice page as a playground and work backwards from what you find there.

Small things worth knowing

  • The numbered circles 1–8 are the eight API types — click one for a simple definition.
  • Examples start closed; click one to open its request, its reply and why it's used.
  • The practice page never contacts a real company — it shows you a simulated answer.
  • The buttons at the top of every page move you between the seven sections.

By the End You'll Be Able To

Four things worth having at the other side of these pages.

Say what an API call isExplain it to a colleague in one plain sentence, without the jargon.
Recognise the eight typesKnow which type a product is using, and the problem it was invented to solve.
Read an API's documentationFind the endpoint, the method and the authorization a call needs.
Send a call yourselfBuild a request, add authorization, and understand the reply that comes back.

Where to Go Next

Keep going in order, or jump to any page from the top menu.