Updating message authorization code
Note: NTLM and Bearer token are only available in Postman native apps.All other authorization types are available in Postman native apps and the Chrome app.Note that the Postman Chrome app is being deprecated.You can use environment, collection, or global variables with all authorization types.In addition to using these in the Postman app, you can also use these authorization types with Newman or Postman monitors.Postman does not save header data and query parameters to prevent sensitive data exposure, such as API keys, to the public.Postman provides authorization types that make it easy for you to handle authentication protocols in Postman native apps.
If you create a new collection or folder, every subsequent request in the parent element inherits the authorization definition, unless the user explicitly selects another type.
This is a string of data specified by the server in the www-Authenticate response header and should be used here unchanged with URLs in the same protection space. When you select “Request Body/Request URL”, Postman checks if the request method is POST or PUT, and if the request body type is x-www-form-urlencoded.
If so, Postman adds authorization parameters to the request body.
To update the collection or folder authorization, click on the ellipses (…) next to the collection or folder name, and select “Edit” to open the modal.
Select the Authorization tab to select an authorization type from the TYPE dropdown.You can select “Add empty parameters to signature” to add empty parameters.