req.body for request payload in Express - Step-by-Step Execution

Concept Flow - req.body for request payload

Client sends HTTP request with payload

↓

Express server receives request

↓

Middleware parses payload

↓

req.body is populated with parsed data

↓

Route handler accesses req.body

↓

Server processes data and sends response

This flow shows how Express receives a request with data, parses it, and makes it available in req.body for your code to use.

Execution Sample

Express

app.use(express.json());

app.post('/data', (req, res) => {
  console.log(req.body);
  res.send('Received');
});

This code sets up Express to parse JSON payloads and logs the received data from req.body.

Execution Table

Step	Action	req.body before	Payload received	req.body after	Output/Effect
1	Client sends POST /data with JSON {"name":"Alice"}	undefined	{"name":"Alice"}	undefined	Request sent to server
2	Express receives request	undefined	{"name":"Alice"}	undefined	Request enters server
3	express.json() middleware parses payload	undefined	{"name":"Alice"}	{"name":"Alice"}	req.body populated
4	Route handler runs, accesses req.body	{"name":"Alice"}	{"name":"Alice"}	{"name":"Alice"}	Logs { name: 'Alice' }
5	Response sent	{"name":"Alice"}	{"name":"Alice"}	{"name":"Alice"}	Client receives 'Received'
6	End	{"name":"Alice"}	{"name":"Alice"}	{"name":"Alice"}	Request cycle complete

💡 Request cycle ends after response is sent

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
req.body	undefined	{"name":"Alice"}	{"name":"Alice"}	{"name":"Alice"}

Key Moments - 2 Insights

Why is req.body empty before the middleware runs?

Because Express does not parse the request payload automatically; the middleware like express.json() must run first to fill req.body, as shown in step 3 of the execution_table.

What happens if the client sends data in a format not handled by middleware?

req.body will remain empty or undefined because the middleware cannot parse the payload, so no data is assigned, as seen before step 3.

Visual Quiz - 3 Questions

Look at the execution_table, what is req.body after the middleware parses the payload?

A {"name":"Alice"}

B {}

C undefined

D null

💡 Hint

Check the 'req.body after' column at step 3 in the execution_table.

At which step does the route handler access req.body?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look for the step where the route handler runs and logs req.body in the execution_table.

If express.json() middleware is removed, what will req.body be in the route handler?

A {}

B undefined

C {"name":"Alice"}

D null

💡 Hint

Refer to the key_moments about middleware parsing and req.body population.

Concept Snapshot

req.body holds parsed request data in Express.
Use middleware like express.json() to fill req.body.
Access req.body inside route handlers to get client data.
Without middleware, req.body is empty or undefined.
Always parse payload before using req.body.

Full Transcript

When a client sends data to an Express server, the data arrives as a raw payload. Express does not automatically parse this data. Middleware such as express.json() reads the payload and converts it into a JavaScript object, storing it in req.body. Route handlers can then access req.body to use the data. Without this middleware, req.body remains empty or undefined. This process ensures your server can read and respond to client data correctly.