~2 min read|
I’ve written in the past about why I like testing my APIs with Postman. Today, I learned that they have yet another feature that makes my life easier — Environment Variables.1
Just like using a variable in a codebase to point to a piece of information that you want to reuse multiple places, Postman variables enable reuse without duplication. They create a single point of entry and management (which I’ve written about as a feature in the past).
Postman offers five different levels of scope1 - which I’m sure will be useful for more power users. For me - the Environment Scope is where I care most — though I can see myself also benefiting from Collections in the future as I work on more and more projects.
With environments being the most useful at this time for me, that’s where I’m focusing.
In this case, I’ve created a
HOST variable so that I can easily switch between my local environment and hitting the endpoints in staging or production.
Using variables is easy and makes managing different environments so much easier than what I was doing before - which included a mix of manual management and maintaining multiple APIs with the environment in the label.
Hi there and thanks for reading! My name's Stephen. I live in Chicago with my wife, Kate, and dog, Finn. Want more? See about and get in touch!