LESSON 0.1

Visible Shape of HTTP

Learn to recognize the basic shape of an HTTP request and response before working with browser tools.

Lesson goal:
When you see something like GET /api/courses 200 OK, you should know what the visible pieces mean.
01 — The Big Picture

HTTP Is a Conversation

A client sends a request. A server sends a response.

REQUEST Client → Server
API / SERVER Processes request
RESPONSE Server → Client
Think: Ask → Server → Answer
02 — Request

The Shape of an HTTP Request

A request tells the server what the client wants to do.

HTTP Request
GET /api/courses/123
Accept: application/json

For now, focus on the first line.

PART 01
Method
PART 02
Endpoint
PART 03
Headers
PART 04
Body
Method

Describes the action the client wants to perform.

GET

In this example: "I want to retrieve something."

Endpoint

Identifies where the request is going.

/api/courses/123

Think: "Which resource am I asking for?"

Headers

Carry additional information about the request.

Accept: application/json

You do not need to memorize headers yet.

Body

Carries data sent with the request when needed.

JSON / form data / other content

Some requests have no body.

03 — Response

The Shape of an HTTP Response

The server answers the request with a response.

HTTP Response
HTTP/1.1 200 OK
Content-Type: application/json

{
  "id": 123,
  "title": "REST API Mastery"
}

Status

200 OK

Tells you the result of the request.

Response Body

Contains the data returned by the server.

{"id":123,"title":"REST API Mastery"}
04 — Connect Them

Request → Response

The two pieces belong together.

GET /api/courses/123
API
200 OK course data
Request = what the client asks.
Response = what the server answers.
05 — One Example

Read This Correctly

Suppose you see:

GET /api/courses/123
404 Not Found
GET
Request method
/api/courses/123
Endpoint
404 Not Found
Response status
Important: The server did respond.

404 means the requested resource was not found.
06 — Status

Status Is the Server's Answer

200

The request succeeded.

404

The requested resource was not found.

For this lesson, you only need to recognize the idea:

Status = result of the request
07 — Mental Model

The Shape You Should Remember

REQUEST Method + URL + optional details
SERVER / API Receives and processes the request
RESPONSE Status + optional data
08 — Quick Check

Can You Read This?

GET /api/lessons/42
200 OK
What is the request method?

✓ Correct. GET is the request method.
Takeaway

Three Things to See

REQUEST
What does the client want?
ENDPOINT
Where is the request going?
STATUS
What happened?
If you can visually recognize these, you already have the foundation for the next lesson.
Next Lesson

Lesson 0.2 — Find API Communication in a Browser

You now know what an HTTP request and response look like. Next, you will use Chrome DevTools to find this communication happening behind a real website.

Understand HTTP
Open DevTools
Find Request