Token management in variables in Postman - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to save the token value into an environment variable.

Postman

pm.environment.set('authToken', [1]);

Drag options to blanks, or click blank then click option'

Apm.environment.get('authToken')

Bpm.request.url

Cpm.response.code

Dpm.response.json().token

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.request.url instead of the response to get the token.

Trying to get the token from environment variable before setting it.

The token is extracted from the JSON response using pm.response.json().token and saved into the environment variable 'authToken'.

2fill in blank

medium

Complete the code to retrieve the stored token from environment variables.

Postman

const token = [1];

Drag options to blanks, or click blank then click option'

Apm.environment.set('authToken')

Bpm.environment.get('authToken')

Cpm.variables.get('authToken')

Dpm.request.headers.get('authToken')

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.environment.set() instead of get() to retrieve the token.

Trying to get token from request headers instead of environment variables.

pm.environment.get('authToken') retrieves the token stored in environment variables.

3fill in blank

hard

Fix the error in the code to correctly set the token variable.

Postman

pm.environment.set('token', [1]);

Drag options to blanks, or click blank then click option'

Aresponse.token

Bpm.response.body.token

Cpm.response.json().token

Dpm.request.body.token

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.response.body.token which is undefined because body is a string.

Trying to get token from pm.request.body which is the request, not response.

pm.response.json().token correctly parses the JSON response and accesses the token property.

4fill in blank

hard

Fill both blanks to create a header with the stored token for authorization.

Postman

pm.request.headers.add({ key: 'Authorization', value: 'Bearer [1]' });
const token = [2];

Drag options to blanks, or click blank then click option'

Apm.environment.get('authToken')

Bpm.environment.set('authToken')

Cpm.response.json().token

Dpm.request.headers.get('Authorization')

Attempts:

3 left

💡 Hint

Common Mistakes

Using pm.environment.set() instead of get() to retrieve the token.

Trying to get token from response instead of environment variables.

The token is retrieved from environment variables using pm.environment.get('authToken') and used in the Authorization header.

5fill in blank

hard

Fill all three blanks to extract the token, save it, and verify it is set correctly.

Postman

const token = [1];
pm.environment.set('authToken', [2]);
pm.test('Token is set', () => pm.expect([3]).to.not.be.undefined);

Drag options to blanks, or click blank then click option'

Apm.response.json().access_token

Btoken

Cpm.environment.get('authToken')

Dpm.response.json().token

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent variable names for token.

Checking the wrong variable in the test assertion.

The token is extracted from pm.response.json().access_token, saved using pm.environment.set with the variable token, and verified by checking pm.environment.get('authToken') is not undefined.

Practice

1. In Postman, why is it useful to store an authentication token in an environment variable?

easy

A. To make the token visible to all users of the Postman app

B. To encrypt the token for security

C. To automatically refresh the token without any scripting

D. To reuse the token across multiple requests without re-authenticating each time

Solution

1. Step 1: Understand token reuse in Postman

   Storing a token in an environment variable allows multiple requests to access it easily without needing to get a new token each time.

2. Step 2: Evaluate other options

   Making the token visible to all users or automatic refresh without scripting is not true by default. Encryption is not automatic either.

3. Final Answer:

   To reuse the token across multiple requests without re-authenticating each time -> Option D

4. Quick Check:

   Token reuse = B [OK]

Hint: Tokens stored in variables enable reuse across requests [OK]

Common Mistakes:

• Thinking tokens auto-refresh without scripts
• Assuming variables encrypt tokens automatically
• Believing tokens are shared with all users by default

2. Which of the following is the correct way to set a token value to an environment variable in Postman test script?

easy

A. pm.environment.set('token', response.token);

B. pm.setEnvironmentVariable('token', response.token);

C. pm.environment.token = response.token;

D. pm.variables.set('token', response.token);

Solution

1. Step 1: Identify the current Postman syntax for setting environment variables

   The correct method is pm.environment.set('variableName', value) in Postman scripts.

2. Step 2: Check other options for correctness

   pm.setEnvironmentVariable is deprecated, direct assignment is invalid, and pm.variables.set sets local variables, not environment variables.

3. Final Answer:

   pm.environment.set('token', response.token); -> Option A

4. Quick Check:

   Use pm.environment.set() to set env variables [OK]

Hint: Use pm.environment.set('name', value) to set env variables [OK]

Common Mistakes:

• Using deprecated pm.setEnvironmentVariable method
• Trying to assign variables directly like pm.environment.token
• Confusing local and environment variables

3. Given this Postman test script snippet after a login request:

let jsonData = pm.response.json();
pm.environment.set('authToken', jsonData.token);

What will be the value of {{authToken}} in the next request if the response JSON is {"token": "abc123"}?

medium

A. null

B. undefined

C. "abc123"

D. pm.response.json()

Solution

1. Step 1: Extract token from response JSON

   The script gets the token value "abc123" from the response JSON using pm.response.json().token.

2. Step 2: Set environment variable 'authToken'

   The token value "abc123" is stored in the environment variable 'authToken' using pm.environment.set.

3. Final Answer:

   "abc123" -> Option C

4. Quick Check:

   Stored token = "abc123" [OK]

Hint: Stored token equals JSON token value from response [OK]

Common Mistakes:

• Assuming variable is undefined if not explicitly declared
• Confusing variable name with function call
• Expecting null instead of actual token string

4. You wrote this test script to save a token:

let jsonData = pm.response.json();
pm.environment.set('token', jsonData.authToken);

But the token is not saved. What is the most likely reason?

medium

A. You must use pm.variables.set instead

B. The response JSON does not have a key named 'authToken'

C. pm.environment.set is deprecated and does not work

D. Tokens cannot be saved in environment variables

Solution

1. Step 1: Check the JSON key used in script

   The script tries to access jsonData.authToken, so the response must have that key.

2. Step 2: Verify if the response JSON contains 'authToken'

   If the response uses a different key like 'token', jsonData.authToken will be undefined and nothing is saved.

3. Final Answer:

   The response JSON does not have a key named 'authToken' -> Option B

4. Quick Check:

   Key mismatch causes undefined token [OK]

Hint: Check JSON key names match exactly in script [OK]

Common Mistakes:

• Assuming pm.environment.set is deprecated
• Using pm.variables.set for environment variables
• Believing tokens can't be saved in environment variables

5. You want to automatically refresh an expired token in Postman by chaining requests. Which approach correctly manages the token variable for reuse?

hard

A. Use a pre-request script in all requests to check token expiry and request a new token if expired, then update the environment variable

B. Manually update the token variable in Postman UI before each request

C. Store the token in a global variable and never update it

D. Hardcode the token in the request headers and do not use variables

Solution

1. Step 1: Understand token expiry handling

   Tokens expire, so scripts must check expiry and refresh tokens automatically to avoid failures.

2. Step 2: Use pre-request scripts to automate token refresh

   Pre-request scripts can check if the token is expired and call the authentication endpoint to get a new token, then update the environment variable.

3. Step 3: Evaluate other options

   Manual updates are error-prone, global variables without updates cause failures, and hardcoding tokens is insecure and inflexible.

4. Final Answer:

   Use a pre-request script in all requests to check token expiry and request a new token if expired, then update the environment variable -> Option A

5. Quick Check:

   Automate token refresh with pre-request scripts [OK]

Hint: Automate token refresh in pre-request scripts [OK]

Common Mistakes:

• Relying on manual token updates
• Using global variables without refresh logic
• Hardcoding tokens in requests