Using extracted data in next request in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the value of the variable after extraction?

You run this Postman test script after a response:

pm.test("Extract userId", () => {
  const jsonData = pm.response.json();
  pm.environment.set("userId", jsonData.user.id);
});

Given the response body:

{"user": {"id": 42, "name": "Alice"}}

What will be the value of the environment variable userId?

A 42 (number)

B "42" (string)

C undefined

D null

💡 Hint

Remember that environment variables in Postman are stored as strings.

Postman environment variables always store values as strings, even if the original data is a number.

❓ assertion

intermediate

Which assertion correctly uses extracted data in the next request?

You extracted a token in the first request and saved it as an environment variable authToken. Which assertion in the next request correctly checks the token is used in the header?

A pm.expect(pm.request.headers.get('Authorization')).to.eql('Bearer ' + pm.environment.get('authToken'));

B pm.expect(pm.request.headers.get('Authorization')).to.eql(`Bearer ${authToken}`);

C pm.expect(pm.request.headers.get('Authorization')).to.eql('Bearer {{authToken}}');

D pm.expect(pm.request.headers.get('Authorization')).to.eql('Bearer authToken');

💡 Hint

Use pm.environment.get to access environment variables in scripts.

To access environment variables in test scripts, use pm.environment.get('authToken'). The header value should be 'Bearer ' plus that token string.

🔧 Debug

advanced

Why does the next request fail to use extracted data?

You extracted a sessionId in the first request with:

pm.environment.set('sessionId', pm.response.json().session.id);

In the next request, you use the header:

Authorization: Bearer {{sessionId}}

But the request fails with unauthorized error. What is the most likely reason?

A The variable sessionId is saved but the next request uses a different environment without that variable.

B The variable sessionId is not available because environment variables require manual saving.

C The variable sessionId was not saved because pm.environment.set was called inside pm.test block.

D The variable sessionId is overwritten by a global variable with empty value.

💡 Hint

Check if the environment selected for the next request is the same as where the variable was saved.

If the next request runs in a different environment, it won't have access to the variable saved in the previous environment.

🧠 Conceptual

advanced

What is the best way to pass extracted data between requests in Postman?

You want to extract a userId from one request and use it in multiple subsequent requests. Which method ensures the data is available across all requests in the collection?

A Save the userId as a global variable using pm.globals.set.

B Save the userId as a local variable in the first request's Tests tab.

C Save the userId as an environment variable using pm.environment.set.

D Save the userId in the request body of the next request manually.

💡 Hint

Local variables only exist during one request execution.

Environment variables persist across requests within the same environment and are best for sharing data between requests.

❓ framework

expert

How to chain requests using extracted data with Postman Collection Runner?

You have a collection with two requests: Login and GetProfile. Login extracts a token and saves it as environment variable token. GetProfile uses this token in the Authorization header.

Which setup ensures the Collection Runner correctly passes the token from Login to GetProfile?

A Run the collection with no environment selected; token is saved globally.

B Run the collection with an environment selected; Login saves token with pm.globals.set; GetProfile uses {{token}} in header.

C Run the collection with an environment selected; Login saves token with pm.variables.set; GetProfile uses {{token}} in header.

D Run the collection with an environment selected; Login saves token with pm.environment.set; GetProfile uses {{token}} in header.

💡 Hint

Collection Runner uses the selected environment to share variables between requests.

Using pm.environment.set saves the token in the selected environment, which is accessible by all requests in the collection run.