Demystifying Postman Variables: HOW and WHEN to use Different Variable Scopes

Are you confused about the different variable types in Postman, like global, collection, environment, local, data variables? Hopefully, this will make your life easier.

== IMPORTANT UPDATE! == With Postman 7.9.0 (October 2019) it is possible to use the pm.* API to create, update or delete collection variables. Download the Postman Quick Reference Guide below to learn how.

___

// P L A Y L I S T S

___

// F R E E R E S O U R C E S

▸▸▸ Download the FREE Postman Quick Reference Guide

___

// P O S T M A N O N L I N E T R A I N I N G

💥 Want to learn more about Postman? Check my Postman online course.

Get it for only $9.99 (limited supply, 75% OFF, first 200 viewers):

___

[dharmiknaik]

Thanks for posting this video. I was looking for this exact thing!

[truthresonator]

Sometimes these videos are even better than that of your paid course because it's more.of.an overview in a short video with the considerations of the choices in mind.

[ismaelfarfan]

The scope of collection and environment should actually be switched just because environment can be shared across all collections in the workspace, just saying.

Environment sounds as a good idea until you end up with 40 possible environments to choose from: {test, test-for-collection1, test-2.0, test1, test-john, my-test, private-test, do-not-touch-test...}.
I wish there was a way to actually pick collection-level variables just as we can pick environment variables.

[pogothemonkey]

as usual, awesome video, thanks for the help! :)

[abhishekkandala]

Hi Valentin Despa. Thanks for this video. Is there any way i can save the assertion status(Pass/Fail) in a variable. I need to pass the assertion status to another request.

[energydrinker]

Cannot get any variables to show using double braces in Pre-request Scripts or Tests. works, but literally outputs "
{{householdId}}" in the console.log. I'm doing a class where pretty much the whole thing is written using the {{}} syntax. Am I doing something wrong? Is there a setting I need to change? Can you no longer access variables with "{{varName}}" in scripts?