Postman apps go through extensive testing and beta builds before we ship. That said, there might be cases when the app crashes, or exhibits unexpected behavior. If you've been unable to troubleshoot the issue on your own, or you can file an issue in the GitHub tracker. If you need to include confidential data in your support request, please visit our support center. Including the app's console logs in your report will provide some helpful data for troubleshooting.
The Postman Console is analogous to a browser's developer console, except that it's tuned for API development. If an API or API test is not behaving as you expect, this would be the place where you will go to deep dive while debugging. As long as the console window is open, all your API activities will be logged here to see what's going on under the hood.
The Postman Console logs the following information:
console.error()from inside scripts.
console.warn() at appropriate locations in the scripts will help extract the exact line of code that is acting up. If you know your way around
To access the console logs, follow these steps:
Viewin the application menu, and click on "Show DevTools".
chrome://flags/#debug-packed-appsin the URL bar in your Chrome browser window.
chrome://inspect/#appsand then click "inspect" just below requester.html under the Postman heading.
View in the application menu, and click on "Show Postman Console" or use the keyboard shortcut (CMD/CTRL + ALT + C) to open. Similar to DevTools, every call along with its headers, network information, and payloads will be logged to the Postman Console.
You can also use the DevTools window to inspect the request and response payloads. If the Interceptor is disabled, switch to the Network tab, and you should see each call as it's made. Clicking on this will let you view the headers and payloads for the requests and responses: