Live Preview on Canary

Hello Post People!
So we have another awesome Canary release we wanted to let you know about.

So what’s new?
Postman makes it easy to make requests by adding headers that are needed in general and ones that browsers and other popular http clients send.
Last year, we made them visible in the form of temporary headers.
However, we heard from you, our users, that this had created some confusion.

So we are introducing something to help with that, known as Live Preview. We will now show you headers that will be sent and tell you how to configure them. These are the headers that will be added to the requests as a result of your requests configuration, such as an authentication method or request body type selected by you. These are just some first steps we are taking to help improve the user experience and functionality of Postman.

How does this impact me?
Creating requests should be very much the way you have known it to be in the past. We have removed the separated “Temporary Headers” vs. “Headers”, now they are all just “Headers”.
We have changed a few things though.
First is, when you do authentication. We have removed the “Preview” button and now when you add an authentication method to your request, it will always be visible as a header to the request.
This same logic applies to things such as cookies. You will see them as a normal header, however you will not be able to directly edit them. They can be edited through the method they were created from.

The next thing you should know is how these headers work. The final request and any headers that were required for Postman to work is, like always, visible in the Postman Console (which, by the way, we reworked to have better experience and contain a tonne of useful info.)

P.S. - As a side note. These changes are not yet reflected in places such as the code generator until the first time the request has been sent.

So, we would love for you to take this for a test run and let us know what you think.
Please reach out to us with your thoughts and input on this new and upcoming feature.

You can download the Canary builds from here -


Hey everyone,

On top of what @tmccann shared, and while we’re adding more helpers directly in the app to make it easier to manage headers, below are more detailed information on how to manage the headers that are sent with your requests.

Click on each entry to see the details.

How to disable the `cookie` header?

If you want to keep cookies in your request from being stored in the cookie jar, open the Settings tabs in your request and toggle Disable cookie jar to ON.

How to disable the `postman-token` header?

The postman-token header helps you track requests coming from Postman on your server, if you want to disable it, head to the general Postman settings, open the General tab, then toggle Send Postman Token header to OFF.

How to disable/override the `no-cache` header?

The no-cache header means a cache will send the request to the origin server for validation before releasing a cached copy (learn more).

To disable it, head to the general Postman settings, open the General tab, then toggle Send no-cache header to OFF.

You can also override the header value by going to the Headers tab of your request, and adding a Cache-Control header with the value you would like (e.g. no-store).

How to override any header?

You can override any header added to your request by going to the Headers tab of your request and adding the header and value you would like to override with (e.g. Cache-Control).

In the coming weeks we’ll be releasing additional helper functionality to provide control over your other request headers—we will keep you posted on progress and will update this FAQ accordingly! In the meantime please feel free to share any feedback you have. :slight_smile: