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.

Practice

1. What does req.params represent in an Express route handler?

easy

A. An object containing query string parameters from the URL

B. An array of middleware functions

C. A function to send responses to the client

D. An object containing route parameters extracted from the URL path

Solution

1. Step 1: Understand the role of req.params

   req.params holds key-value pairs for parameters defined in the route path, extracted from the URL.

2. Step 2: Differentiate from other request properties

   Query parameters are accessed via req.query, not req.params. Response functions and middleware arrays are unrelated.

3. Final Answer:

   An object containing route parameters extracted from the URL path -> Option D

4. Quick Check:

   req.params = route parameters [OK]

Hint: Remember: req.params gets values from URL path, not query [OK]

Common Mistakes:

• Confusing req.params with req.query
• Thinking req.params is a function
• Assuming req.params contains request body data

2. Which of the following is the correct way to define a route with a parameter named id in Express?

easy

A. app.get('/user/*id', (req, res) => { ... })

B. app.get('/user/id', (req, res) => { ... })

C. app.get('/user/:id', (req, res) => { ... })

D. app.get('/user/?id', (req, res) => { ... })

Solution

1. Step 1: Recognize route parameter syntax

   Express uses a colon : before the parameter name in the route path to define route parameters.

2. Step 2: Evaluate each option

   app.get('/user/:id', (req, res) => { ... }) correctly uses /:id. Options A, B, and C use incorrect syntax for route parameters.

3. Final Answer:

   app.get('/user/:id', (req, res) => { ... }) -> Option C

4. Quick Check:

   Route params start with ':' [OK]

Hint: Use ':' before param name in route path [OK]

Common Mistakes:

• Omitting the colon before parameter name
• Using query syntax instead of route param syntax
• Using wildcard '*' incorrectly

3. Given the route definition app.get('/product/:productId', (req, res) => { res.send(req.params.productId); });, what will be the response when a client requests /product/12345?

medium

A. The string '12345'

B. An error because productId is undefined

C. The string '/product/12345'

D. An empty response

Solution

1. Step 1: Understand route parameter extraction

   The route defines a parameter productId which captures the part of the URL after /product/.

2. Step 2: Check what is sent in the response

   The handler sends req.params.productId, which will be the string '12345' from the URL.

3. Final Answer:

   The string '12345' -> Option A

4. Quick Check:

   req.params.productId = '12345' [OK]

Hint: req.params.paramName matches URL part after ':' [OK]

Common Mistakes:

• Expecting full URL or path in req.params
• Confusing req.params with req.query
• Assuming undefined if param not accessed correctly

4. Consider this Express route: app.get('/order/:orderId', (req, res) => { const id = req.params.id; res.send(id); }); What is the problem with this code?

medium

A. req.params cannot be used in GET routes

B. The route parameter is named orderId but accessed as id, causing undefined

C. The route path is missing a parameter

D. res.send cannot send strings

Solution

1. Step 1: Compare route parameter name and access key

   The route defines parameter orderId, but the code accesses req.params.id, which does not exist.

2. Step 2: Understand the effect of this mismatch

   Accessing req.params.id returns undefined, so res.send(id) sends 'undefined'.

3. Final Answer:

   The route parameter is named orderId but accessed as id, causing undefined -> Option B

4. Quick Check:

   Param name mismatch causes undefined [OK]

Hint: Access req.params using exact route param name [OK]

Common Mistakes:

• Using wrong parameter name in req.params
• Assuming req.params works like req.body
• Ignoring case sensitivity in parameter names

5. You want to create an Express route that accepts two parameters: category and itemId. Which code correctly defines the route and sends back a JSON object with both parameters?

hard

A. app.get('/shop/:category/:itemId', (req, res) => { res.json({ category: req.params.category, itemId: req.params.itemId }); });

B. app.get('/shop/:category/:itemId', (req, res) => { res.json({ category: req.query.category, itemId: req.query.itemId }); });

C. app.get('/shop/:category/:itemId', (req, res) => { res.json({ category: req.params.category, itemId: req.query.itemId }); });

D. app.get('/shop/:category/:itemId', (req, res) => { res.json({ category: req.body.category, itemId: req.body.itemId }); });

Solution

1. Step 1: Define route with two parameters

   The route path /shop/:category/:itemId correctly defines two route parameters.

2. Step 2: Access parameters from req.params

   Both category and itemId must be accessed from req.params to get values from the URL path.

3. Step 3: Verify response sends JSON with both parameters

   app.get('/shop/:category/:itemId', (req, res) => { res.json({ category: req.params.category, itemId: req.params.itemId }); }); sends a JSON object with both parameters from req.params. Other options incorrectly use req.query or req.body.

4. Final Answer:

   app.get('/shop/:category/:itemId', (req, res) => { res.json({ category: req.params.category, itemId: req.params.itemId }); }); -> Option A

5. Quick Check:

   Use req.params for route params, send JSON [OK]

Hint: Use req.params for all route parameters in URL path [OK]

Common Mistakes:

• Mixing req.params with req.query or req.body
• Not defining all parameters in route path
• Sending plain text instead of JSON when needed