LESSON 0.2

Find API Communication in a Browser

Discover where HTTP communication happens behind a real website.

Lesson goal:
Find the API request made by a website using Chrome DevTools.

HTTP Is Communication

In Lesson 0.1, you learned the visible shape of HTTP:

Request
API / Server
Response

Now we will find this communication inside a website.

Start With a Website

Imagine that you open a learning website.

https://learning.example.com/course

REST API MASTERY

Learn REST APIs through hands-on practice.

You can see the website. But the API communication is normally hidden behind this interface.

Open Chrome DevTools

Now we will use the actual Chrome browser interface. You do not need to understand all of DevTools.

For this lesson, we only need one place: the Network panel.
1

Open the website in Google Chrome

First, open the website that you want to investigate.

🖱 Website page

Keep this page open. We will watch what happens when the browser communicates with a server.

2

Open Chrome DevTools

There are several ways to open DevTools. For this lesson, the easiest is:

🖱 Right-click the webpage → Inspect

You can also use the keyboard shortcut:

Ctrl + Shift + I

DevTools will appear attached to the browser window.

3

Look at the DevTools tabs

DevTools contains several panels. You may see tabs such as:

Chrome DevTools
Elements
Console
Sources
Network
Performance
Application

Do not worry about the other tabs.

👉 Look for:
Network
4

Click Network

Click the Network tab.

🖱 Network

The Network panel records network activity from the page.

5

Now use the website

Keep the Network panel open. Then perform an action on the website.

Website
User Action
Network Request

For example, click a button that loads lessons, products, comments, or other data.

6

Watch the request appear

After the action, new rows may appear in the Network panel.

Elements
Console
Network
All
Fetch/XHR
Doc
JS
Img
Name Type Status
index.html document 200
app.js script 200
lessons fetch 200
👉 What are we looking for?

A request related to the action we just performed.

The whole GUI workflow

🌐 Website
🖱 User Action
🛠 DevTools
Network
Network
Request
API
You are not learning DevTools for its own sake.

You are using DevTools as a window to see HTTP communication that normally stays behind the website.

Simulate the Website Action

In a real website, you would perform an action while the Network panel is open.

Find the New Request

Look at the simulated Network panel. The request related to our action is:

Elements
Console
Sources
Network
Name Type Status
index.html document 200
app.js script 200
lessons fetch 200
Request Method
GET
Request URL
https://example.com/api/lessons
Status Code
200 OK

Try it: Click the lessons request above.

✓ You found the API communication

The website action caused the browser to request data from an API.

GET /api/lessons 200 OK

What Did We Actually Find?

User Action
Browser
API Request

The important discovery is not the DevTools interface.

A website action can cause the browser to communicate with an API.

See the Hidden Communication

User
Website
Browser
API
Response
API
Browser

DevTools gives you a window into this communication.

Remember These 3 Things

1. Open DevTools
Right-click the page → Inspect.
2. Open Network
Network shows the browser's network activity.
3. Perform an action
Watch for the request caused by that action.

Lesson 0.3 — Read Request and Response Details

You have now learned how to find the request. Next, you will learn how to read what is inside it.

Find Request
Read Request
Read Response