req.params for route parameters in Express - Step-by-Step Execution

Concept Flow - req.params for route parameters

Client sends request to URL with parameters

↓

Express matches route pattern

↓

Extract parameters from URL

↓

Store parameters in req.params object

↓

Route handler accesses req.params

↓

Use parameters to process request and send response

This flow shows how Express extracts parts of the URL as parameters and makes them available in req.params for the route handler to use.

Execution Sample

Express

app.get('/user/:id', (req, res) => {
  res.send(`User ID is ${req.params.id}`);
});

This code defines a route that captures the user ID from the URL and sends it back in the response.

Execution Table

Step	Request URL	Route Pattern	req.params Content	Action	Response Sent
1	/user/42	/user/:id	{ id: '42' }	Extract id=42 from URL	User ID is 42
2	/user/abc	/user/:id	{ id: 'abc' }	Extract id=abc from URL	User ID is abc
3	/user/	/user/:id	{}	No id parameter found	No matching route or error
4	/user/123/profile	/user/:id	{}	No match due to extra path segment	No matching route or error

💡 Execution stops after sending response for matched route or no match found.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
req.params	{}	{ id: '42' }	{ id: 'abc' }	{}	{}

Key Moments - 2 Insights

Why is req.params empty when the URL does not include the parameter?

Because the route pattern expects a parameter at that position. If the URL misses it, Express does not match the route, so req.params remains empty as shown in step 3.

What happens if the URL has extra parts beyond the route pattern?

Express matches only the defined route pattern. Extra parts cause no match or are ignored depending on route setup, so req.params only contains parameters from the matched pattern as in step 4.

Visual Quiz - 3 Questions

Look at the execution table, what is req.params when the URL is '/user/abc'?

A { user: 'abc' }

B {}

C { id: 'abc' }

D null

💡 Hint

Check row 2 under 'req.params Content' in the execution table.

At which step does the route not match because the parameter is missing?

A Step 3

B Step 1

C Step 4

D Step 2

💡 Hint

Look for the step where req.params is empty and no parameter is extracted.

If the route pattern was '/user/:id/profile', what would req.params be for URL '/user/123/profile'?

A {}

B { id: '123' }

C { profile: '123' }

D null

💡 Hint

Think about how parameters match named parts in the route pattern.

Concept Snapshot

Express route parameters are parts of the URL marked with :name.
They are extracted and stored in req.params as key-value pairs.
Use req.params.name inside route handlers to access them.
If URL does not match pattern, req.params is empty.
Extra URL parts beyond pattern do not affect req.params.

Full Transcript

In Express, when a client sends a request to a URL that matches a route with parameters, Express extracts those parameters from the URL and stores them in the req.params object. For example, if the route is '/user/:id' and the URL is '/user/42', then req.params will be { id: '42' }. The route handler can then use req.params.id to get the value '42' and respond accordingly. If the URL does not include the parameter or does not match the route pattern, req.params will be empty. Extra parts in the URL beyond the route pattern are ignored or cause no match depending on the route setup. This process allows dynamic URLs where parts can change and be accessed easily in the code.