I just found out I've been heavily underusing Postman - the Postman team has baked in a Node.js environment that allows for scripting before and after...
I just found out I've been heavily underusing Postman - the Postman team has baked in a Node.js environment that allows for scripting before and after requests 🤯. This provides a TON of capability within an API tool, and I want to highlight what I've been embarrassingly doing for a year + :
1. Send a request to grab a token or form of auth (example client creds flowTwitch API)
2. Highlight and copy the response token
3. Navigate to the next request, paste the token in the appropriate location
4. Submit second request and get a response
But with scripts there is a simple way to automate the process of getting a token.
In the "Tests" tab of the GET token call, we can place the following:
var jsonData = JSON.parse(responseBody);
console.log(jsonData);
pm.globals.set("oauthToken", jsonData.access_token);Snippets placed in the "Tests" tab will get run after the request is executed, so here we are setting the global variable oauthToken to the key access_token in the response JSON we got from the client creds flow. This value is now available for use like any other environment variable in Postman with the double curly bracket syntax {{oauthToken}}, removing the need for the copy-paste across requests:
This small trick alone has sped up how I use Postman and there's a whole lot more you can do in these scripts... Why not use fetch in the "Pre-request Scripts" tab to completely remove the need for the first request to get the token?