What's new in Postman 7.26?

Happy Monday folks! :smiley:

You’ll never guess what… we’ve just released Postman 7.26! So grab the latest version from our website, or update your app, and read on to see which new features that version brings. :open_book:

Axios code snippets!

We have some great news for Axios users, you can now generate code snippets for Axios directly from Postman! Once you’re happy with your request and ready to try it out in your app, click Code, and search for NodeJs - Axios in the list.

If you didn’t know you can use Postman to generate code snippets in many languages, @joyce just recorded a demo video that teaches you everything you need to know about it, watch it here. :tv:

Better token management for OAuth 2.0

OAuth 2.0 is “the industry-standard protocol for authorization” (source), and it is widely use to authenticate against APIs. We’ve added new ways to manage your OAuth 2.0 tokens within Postman, specifically you can now:

  • Delete all your tokens
  • Delete all your expired tokens only

To do so, navigate to Manage Tokens, open the dropdown next to All Tokens, then select either All Tokens or Expired Tokens.

Improvements to variables in request body

We’ve made it easier to use Postman variables in the body of requests. When entering variables, you’ll now be prompted with name suggestions, including the current value of the variable. On top of that, if you’re using JSON you’ll get extra syntax highlighting and formatting!

You can try it out by editing the body of a request and entering either a variable that is saved in the collection, environment, or globally, or you can try using one of the dynamic variables (e.g. {{$randomBs}}).

As usual, these are only the highlights. If you’d like to see the full lists of improvements and bug fixes that were also part of that release, you can find the full release notes here. :slightly_smiling_face:

Hope you’ll enjoy this release and let us know if you have any feedback!

7 Likes

It seems as though you’ve changed how environment variables are saved, and how they are used.

We had been using
API-KEY apiKey=abcdefgh

in the environment, and using it in the individual tests like

{{HOST}}/endpoint?{{API-KEY}}

and that worked until… today.

Today, the {{API-KEY}} is being subbed in the query as

https://hostname.com/endpoint?apiKey=abcdefgh=

That final = is making my tests all fail. Our system says “API Key is not valid.” because the API key is abcdefgh, not abcdefgh=.

When I diff my export (we export to save in Git), our previous collection file had

“query”: [
{
“key”: “{{API-KEY}}”,
“value”: null
},

It now has

“query”: [
{
“key”: “{{API-KEY}}”,
“value”: “”
},

So… while we recognize that this is closer to correct and we should have perhaps done this all along, we’d like to know

  • Is this a bug?
  • If a bug, is there an estimate as to when it’ll be fixed?
  • Or is it a feature :slight_smile: and we need to change our tests to comply with this sort of setup?

Thanks.

Hi!
Postman started to freeze if I send larger debug data in the response (Symfony dump() command). I tried version 7.23 and that works perfectly fine.
Is there a way to stop 7.23 from automatically updating to the current version? Or is there some new option I might disable to overcome the freezing?
Now basically I can’t use this version but I think any 7.* version will updated to this version and 6.* versions seem unable to sync my workspace.
Any suggestions?

@jennievh I wasn’t able to replicate that issue, does this happen with any value set for {{API-KEY}}? Which type of API key are you using, is it base64 encoded? Ideally if you could share a collection and environment that would allow us to replicate it that would help!

@glnemeth Could you send an email to our support on help@postman.com attaching the logs from your app? (see https://support.getpostman.com/hc/en-us/articles/360033270134-Where-can-I-find-logs-for-the-Postman-app-)

Hi @jennievh

I was unable to reproduce your problem locally in the latest version. Can you please confirm that your request URL does not have = in the end. Means how does your request URL looks in the latest app:

  1. {{HOST}}/endpoint?{{API-KEY}}
                            or
  2. {{HOST}}/endpoint?{{API-KEY}}=

If it is looking like option 1 then it might be a bug. In that case, I would like to have a look at your collection. It would be great if you can show both the old and newly exported collection in Collection v1 as well as Collection v2 formats.