I've been working with postman for the past couple months while developing an api only Ruby on Rails application. We've been using shared teams in order to distribute changes and updates to the api as it grew. We've found massive value in both variables and scripts within postman.


Most urls contain variable values in them for example


This is then obtained as a variable by the api and used to return or update the correct resource on the server. Maintaining this in Postman is a doddle, firstly set the url to use a variable


Then setup and environment (Eye icon in top right), add the order_number variable you wish to use and postman will use this when making the calls.

This is great if you have a large api with lots of calls you need to maintain all the variables, lets you configure your setup in one place. You can then share those enviroments too.


The second main area we found useful is scripts, labeled "Tests" in postman.

The API we were working on has a token with quite a short expiry, and it is supplied in the header for each request, it would take us as long as the expiry time to go round all requests and update it, however, combine this with variables, it makes the job easy.

jsonData = JSON.parse(responseBody)  
postman.setEnvironmentVariable("token", jsonData.auth_token);  

This allows us to just call the login endpoint and it will automatically set the environment variable.

Postman is a great tool for teams building an api, however, I do think that the pricing model jumps up pretty quickly.