APIs are just waiters between you and the kitchen.

If the old version felt like being handed a dictionary before dinner, this one fixes that. We’ll start with a restaurant, make a real request, and only then introduce the proper names.

No coding needed to follow along
Real live demos
Glossary moved to the end
01

What is an API?

Think of an API like a waiter in a restaurant. You don’t walk into the kitchen yourself — you tell the waiter what you want, and they bring back the result.

The restaurant scene Click an order and watch the API waiter carry your request to the kitchen.
You = app or website Waiter = API Kitchen = server + database Menu = documentation
Customer side
Kitchen side
📋

Menu

The menu is the documentation. It shows what can be ordered.

🙋

You

The app asks for something useful: a profile, a post, a todo, a photo.

👨‍🍳

Kitchen

The server looks things up, prepares a response, or says something went wrong.

🧑‍🍳
API waiter
Right now: Open the menu, choose something, and watch the trip. Latest response: Nothing ordered yet.

Try placing an order

These orders map directly to real API ideas, but we’ll keep the restaurant language first.

Sometimes the kitchen says yes. Sometimes it says “we’re out of that dish.” That’s what errors are.
1. Look at the menu You check what the restaurant offers. In API land, that’s reading the docs.
2. Tell the waiter You make a request. The waiter carries it to the kitchen.
3. Get the result The kitchen sends back food — or an explanation if something went wrong.
📋

Menu

API documentation shows what you can ask for and how to ask for it.

💬

Your request

You ask for something specific, like one user profile or one todo item.

🍝

The response

The result comes back in a structured format your app can read.

🚫

Sometimes no

If the dish doesn’t exist or you’re not allowed to order it, you get an error.

02

Your first request

Now let’s map the restaurant story to the real thing. Ordering a user’s profile is called a GET request — like asking the waiter to bring you the menu item for user #1.

Story → real API

"I want that person’s profile"You ask for one thing.
→
GET /users/1A GET request asks to read data.
The menuIt tells you what’s available.
→
API docsThey show endpoints and formats.
The waiter returns your dishYou get something back.
→
JSON responseThe server sends data back as structured text.

Live demo

GET
Waiting to send
No request yet
Click “Send request” to fetch live data from jsonplaceholder.typicode.com.

Plain-English breakdown

Once the response arrives, this panel will explain what each piece means in normal language.

03

The four actions

These are the four most common things apps do with data. We’ll keep the restaurant analogy attached so the terms never float off into jargon-land.

Choose one action above.
Request

        

        

          
Response

          

        

      

    

  


  

    
04

    
Did it work?

    

      Status codes are the kitchen’s quick answer. Tap any card to flip it and see the real code plus what it means.
    


    

    
Front = restaurant version. Back = real API version.

  


  

    
05

    
Proving who you are

    

      Sometimes the restaurant lets anyone sit down. Sometimes it wants a membership card, a wristband, or a trusted introduction. That’s authentication.
    


    

    

  


  

    
06

    
Reading the response

    

      JSON is just a tidy way to label information. Click around to see what each line means, starting simple and then getting a little more nested.
    


    

    

      

      

        
Hover or tap a line

        
We’ll explain what that part of the response means in plain English.

      

    

  


  

    
07

    
Glossary

    

      Now the terms are here when you need them. Use this as a reference, not as the front door.
    


    

      🔍
      
    


    

    

    
No terms match that search.