Requests show the literal {{baseUrl}} or {{token}} text instead of the resolved value, causing 404s or authentication failures, even though the variable appears to be defined.

Verify the correct environment is actually selected and understand variable scope precedence between global, environment, and collection levels.

Step-by-Step Guide

1

Check the environment dropdown in the top-right is set to the intended environment, not 'No Environment'

2

Confirm the variable name matches exactly, including case, in both definition and {{usage}}

3

Remember scope precedence: local > data > environment > collection > global

4

Use the eye icon to preview the currently resolved values before sending

5

For dynamic tokens, set them via a script in the Tests tab: pm.environment.set('token', response.token)

6

Avoid wrapping {{variable}} in quotes inside raw JSON unless the value itself needs them

7

Sync environments across the team using a shared Postman workspace instead of manual exports

Found an issue with this solution?

Related Topics

postman pre request scriptspostman collection runner variablespostman team workspace sync