Variable syntax ({{variable}}) in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the syntax {{variable}} represent in Postman?

It represents a placeholder for a variable value that Postman will replace during request execution. This allows dynamic data to be used in requests.

beginner

How do you define a variable that can be used with {{variable}} syntax in Postman?

You define variables in Postman environments, collections, or globals. Once defined, you can reference them using {{variable}} in your requests.

intermediate

What happens if a variable used with {{variable}} syntax is not defined in Postman?

Postman will send the request with the literal string {{variable}} if the variable is not defined, which usually causes the request to fail or behave unexpectedly.

intermediate

Can you use {{variable}} syntax inside Postman scripts (Pre-request or Tests)?

No, inside scripts you use JavaScript to access variables via Postman API like pm.variables.get('variable'). The {{variable}} syntax is only for request URLs, headers, or bodies.

beginner

Why is using {{variable}} syntax helpful in API testing with Postman?

It allows you to reuse requests with different data easily, supports environment switching, and helps automate tests by injecting dynamic values.

What does {{username}} do in a Postman request?

A Creates a new variable named 'username'

B Inserts the value of the variable 'username' defined in Postman

C Comments out the line in the request

D Sends the literal text '{{username}}' in the request

The syntax {{username}} tells Postman to replace it with the value of the variable 'username' during request execution.

Where can you define variables used with {{variable}} syntax in Postman?

A In environments, collections, or globals

B Only in the request body

C Only inside test scripts

D In the URL bar of the browser

Variables can be defined in Postman environments, collections, or global variables to be used with {{variable}} syntax.

What happens if a variable used with {{variable}} is not defined?

A Postman replaces it with an empty string

B Postman throws an error and stops the request

C Postman sends the literal text '{{variable}}' in the request

D Postman automatically creates the variable with a default value

If the variable is not defined, Postman sends the literal string '{{variable}}', which usually causes the request to fail.

Can you use {{variable}} syntax inside Postman test scripts?

A No, you must use JavaScript methods like pm.variables.get()

B Yes, it works the same as in requests

C Yes, but only for global variables

D No, variables cannot be accessed in scripts

Inside scripts, you access variables using JavaScript methods like pm.variables.get('variable'), not {{variable}} syntax.

Why is using {{variable}} syntax useful in API testing?

A It makes requests slower

B It disables authentication automatically

C It encrypts the request data

D It allows dynamic data reuse and environment switching

Using {{variable}} syntax helps reuse requests with different data and switch environments easily, improving test automation.

Explain how the {{variable}} syntax works in Postman and where you define these variables.

Think about how Postman replaces text before sending the request.

Describe what happens if you use {{variable}} in a request but the variable is not defined in Postman.

Consider what Postman does when it cannot find a variable value.

Practice

1. What is the correct way to use a variable named userId in a Postman request URL?

easy

A. Use $userId in the URL to insert the variable value.

B. Use [userId] in the URL to insert the variable value.

C. Use {{userId}} in the URL to insert the variable value.

D. Use userId directly without any special syntax.

Solution

1. Step 1: Understand Postman variable syntax

   Postman uses double curly braces {{variable}} to insert variable values dynamically.

2. Step 2: Apply syntax to the variable userId

   To use the variable userId, you write {{userId}} in the request URL or body.

3. Final Answer:

   Use {{userId}} in the URL to insert the variable value. -> Option C

4. Quick Check:

   Variable syntax = {{variable}} [OK]

Hint: Remember variables always use double curly braces {{}} [OK]

Common Mistakes:

• Using single brackets or dollar sign instead of {{}}
• Writing variable name without any braces
• Confusing variable syntax with other languages

2. Which of the following is the correct syntax to reference a variable named token in Postman?

easy

A. {token}

B. {{token}}

C. [[token]]

D. $token

Solution

1. Step 1: Recall Postman variable syntax rules

   Postman requires variables to be wrapped in double curly braces to be recognized.

2. Step 2: Match the correct syntax for variable token

   The correct syntax is {{token}}, which tells Postman to replace it with the variable's value.

3. Final Answer:

   {{token}} -> Option B

4. Quick Check:

   Variable reference = {{variable}} [OK]

Hint: Always use double curly braces {{}} for variables [OK]

Common Mistakes:

• Using single braces or brackets
• Using dollar sign prefix
• Forgetting braces entirely

3. Given the environment variable baseUrl is set to https://api.example.com, what will be the full URL when the request uses {{baseUrl}}/users?

medium

A. https://api.example.comusers

B. {{baseUrl}}/users

C. https://api.example.com{{baseUrl}}/users

D. https://api.example.com/users

Solution

1. Step 1: Understand variable substitution in Postman

   Postman replaces {{baseUrl}} with its set value before sending the request.

2. Step 2: Substitute {{baseUrl}} with its value

   Since baseUrl is https://api.example.com, the URL becomes https://api.example.com/users.

3. Final Answer:

   https://api.example.com/users -> Option D

4. Quick Check:

   Variable replaced URL = https://api.example.com/users [OK]

Hint: Variables replace exactly with their set values [OK]

Common Mistakes:

• Not replacing variable and leaving {{baseUrl}} as is
• Concatenating variable value incorrectly
• Missing slash between baseUrl and path

4. You wrote Authorization: Bearer {token} in the headers, but the token is not replaced. What is the error?

medium

A. Variable syntax is incorrect; should be {{token}}.

B. Token variable is not set anywhere.

C. Bearer keyword is missing.

D. Headers do not support variables.

Solution

1. Step 1: Check the variable syntax in the header

   The header uses {token} which is missing one pair of curly braces.

2. Step 2: Correct the syntax to {{token}}

   Postman requires double curly braces to recognize variables, so it should be Authorization: Bearer {{token}}.

3. Final Answer:

   Variable syntax is incorrect; should be {{token}}. -> Option A

4. Quick Check:

   Correct variable syntax = {{variable}} [OK]

Hint: Always use double curly braces {{}} for variables in headers too [OK]

Common Mistakes:

• Using single braces instead of double
• Assuming variables auto-replace without braces
• Not setting the variable value before use

5. You want to reuse a variable sessionId inside a JSON body and a header in Postman. Which is the best practice to ensure it works correctly?

hard

A. Set sessionId as an environment variable and use {{sessionId}} in both places.

B. Write sessionId value directly in JSON and header without variables.

C. Use different variable syntaxes in JSON and header for safety.

D. Set sessionId only in the header; JSON will inherit it automatically.

Solution

1. Step 1: Understand variable scope and reuse in Postman

   Environment variables are accessible throughout the request, including headers and body.

2. Step 2: Use consistent variable syntax {{sessionId}} in both JSON body and header

   This ensures Postman replaces the variable correctly wherever it appears.

3. Final Answer:

   Set sessionId as an environment variable and use {{sessionId}} in both places. -> Option A

4. Quick Check:

   Use environment variables + {{variable}} syntax for reuse [OK]

Hint: Set once as environment variable, use {{variable}} everywhere [OK]

Common Mistakes:

• Hardcoding values instead of variables
• Using inconsistent variable syntax
• Assuming variables auto-share without setting scope