Path parameters in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Path Parameters in API Requests

In Postman, what is the primary purpose of using path parameters in an API request URL?

A To define the request body format

B To specify dynamic parts of the URL that identify specific resources

C To add query filters to the API request

D To set HTTP headers for authentication

💡 Hint

Think about how URLs change to access different items in a collection.

Path parameters are used to specify dynamic segments in the URL that point to specific resources, like user IDs or product codes.

❓ Predict Output

intermediate

Output of a Postman Request with Path Parameters

Given the API endpoint https://api.example.com/users/:userId/orders/:orderId and path parameters userId=42 and orderId=1001, what is the final URL sent by Postman?

A https://api.example.com/users/1001/orders/42

B https://api.example.com/users/:userId/orders/:orderId

C https://api.example.com/users?userId=42&orderId=1001

D https://api.example.com/users/42/orders/1001

💡 Hint

Path parameters replace placeholders in the URL path, not query strings.

Path parameters replace the placeholders in the URL path with actual values, forming the final URL.

❓ assertion

advanced

Validating Path Parameter Usage in Postman Tests

Which Postman test script assertion correctly verifies that the userId path parameter in the request URL is 123?

Postman

pm.test('UserId path parameter is 123', () => {
  const url = pm.request.url.toString();
  // Assertion here
});

A pm.expect(pm.request.url.path[1]).to.eql('123');

B pm.expect(pm.request.url.query.get('userId')).to.eql('123');

C pm.expect(pm.request.url.variables.get('userId')).to.eql('123');

D pm.expect(url).to.include('/users/123/');

💡 Hint

Path parameters appear in the URL path array, not in query or variables directly.

In Postman, pm.request.url.path is an array of path segments. The userId is usually the second segment if the path is like /users/123.

🔧 Debug

advanced

Debugging Path Parameter Replacement Issue

A Postman request URL is https://api.example.com/items/:itemId/details. The path parameter itemId is set to 789, but the request is sent with the URL https://api.example.com/items/:itemId/details (no replacement). What is the most likely cause?

A The path parameter <code>itemId</code> was not defined in the Postman collection or environment variables

B The HTTP method is incorrect and prevents path parameter substitution

C The request body is missing, causing the URL to not update

D The server is rejecting the request and returning the original URL

💡 Hint

Check if the variable name matches exactly and is defined.

If the path parameter variable is not defined in Postman environment or collection variables, Postman cannot replace the placeholder in the URL.

❓ framework

expert

Automating Tests for Path Parameters in Postman Collections

Which approach best automates testing multiple path parameter values in a Postman collection run?

A Write a pre-request script that randomly generates path parameter values without external data files

B Manually change the path parameter value in the URL before each request and run the collection multiple times

C Use a Postman collection runner with a CSV file containing different path parameter values and reference them in the URL

D Use Postman monitors to schedule requests without changing path parameters

💡 Hint

Think about how to run the same request multiple times with different inputs automatically.

Using the collection runner with a CSV file allows you to supply multiple sets of path parameter values and run tests automatically for each set.

Practice

1. What is the purpose of path parameters in a URL when testing APIs in Postman?

easy

A. To specify the HTTP method

B. To add headers to the request

C. To make URLs dynamic by allowing variable parts

D. To set the request body content

Solution

1. Step 1: Understand URL structure in APIs

   URLs can have fixed and variable parts. Variable parts are called path parameters.

2. Step 2: Role of path parameters in Postman

   Path parameters allow you to replace parts of the URL dynamically to test different data.

3. Final Answer:

   To make URLs dynamic by allowing variable parts -> Option C

4. Quick Check:

   Path parameters = dynamic URL parts [OK]

Hint: Path parameters make URLs flexible by using placeholders [OK]

Common Mistakes:

• Confusing path parameters with headers
• Thinking path parameters set HTTP methods
• Mixing path parameters with request body

2. Which of the following is the correct syntax to define a path parameter in a Postman request URL?

easy

A. /users/{userId}

B. /users/:userId

C. /users/[userId]

D. /users/<userId>

Solution

1. Step 1: Identify path parameter syntax in Postman

   Postman uses curly braces {} to mark path parameters in URLs.

2. Step 2: Compare options

   Only /users/{userId} uses curly braces correctly: /users/{userId}.

3. Final Answer:

   /users/{userId} -> Option A

4. Quick Check:

   Curly braces = path parameters in Postman [OK]

Hint: Use curly braces {} for path parameters in URLs [OK]

Common Mistakes:

• Using colon : instead of curly braces
• Using square brackets [] or angle brackets <>
• Omitting braces around parameter name

3. Given the Postman request URL https://api.example.com/users/{userId}/posts/{postId} and path parameters userId=42 and postId=7, what is the final URL sent by Postman?

medium

A. https://api.example.com/users/42/posts/7

B. https://api.example.com/users/{42}/posts/{7}

C. https://api.example.com/users/userId/posts/postId

D. https://api.example.com/users/7/posts/42

Solution

1. Step 1: Replace each path parameter with its value

   Replace {userId} with 42 and {postId} with 7 in the URL.

2. Step 2: Construct the final URL

   The URL becomes https://api.example.com/users/42/posts/7 after substitution.

3. Final Answer:

   https://api.example.com/users/42/posts/7 -> Option A

4. Quick Check:

   Substitute parameters correctly = final URL [OK]

Hint: Replace each {param} with its value exactly [OK]

Common Mistakes:

• Leaving curly braces in final URL
• Swapping parameter values
• Using parameter names instead of values

4. You wrote the URL https://api.example.com/items/{itemId} in Postman but forgot to set the path parameter itemId. What will happen when you send the request?

medium

A. Postman removes the {itemId} part from the URL

B. Postman automatically replaces {itemId} with 0

C. Postman prompts you to enter the missing parameter before sending

D. Postman sends the URL with {itemId} unchanged, causing a 404 or error

Solution

1. Step 1: Understand missing path parameter behavior

   If a path parameter is not set, Postman does not replace it automatically.

2. Step 2: Effect on request URL and response

   The URL is sent with {itemId} literally, likely causing server error or 404.

3. Final Answer:

   Postman sends the URL with {itemId} unchanged, causing a 404 or error -> Option D

4. Quick Check:

   Unset path parameter = URL unchanged, error likely [OK]

Hint: Always set all path parameters before sending requests [OK]

Common Mistakes:

• Assuming Postman auto-fills missing parameters
• Expecting Postman to remove missing parameters
• Thinking Postman prompts automatically

5. You want to test an API endpoint /orders/{orderId}/items/{itemId} in Postman. You have a list of order IDs and item IDs. Which approach correctly tests all combinations using path parameters?

hard

A. Manually replace path parameters for each combination and send requests one by one

B. Use Postman collection runner with a CSV file containing orderId and itemId columns

C. Write all URLs with parameters hardcoded and import them as separate requests

D. Use environment variables but only set one parameter at a time

Solution

1. Step 1: Understand testing multiple parameter combinations

   Testing all combinations manually is slow and error-prone.

2. Step 2: Use Postman collection runner with CSV data

   CSV file with columns orderId and itemId lets Postman run requests for each row, replacing path parameters automatically.

3. Final Answer:

   Use Postman collection runner with a CSV file containing orderId and itemId columns -> Option B

4. Quick Check:

   Collection runner + CSV = efficient parameter testing [OK]

Hint: Use collection runner with CSV for multiple path parameter tests [OK]

Common Mistakes:

• Testing combinations manually one by one
• Hardcoding URLs instead of using parameters
• Setting only one parameter in environment variables