Postman Console Debugging

Requests fail for reasons that the response panel does not always reveal. A header may not leave Postman the way you expected. A script may stop halfway. A variable may hold the wrong value. The Postman Console shows everything that happens behind the scenes, and it turns guesswork into evidence.

The Dashboard Camera Idea

A car dashboard camera records the full journey, not only the crash. The console works the same way. It records the real request that left your computer, the raw response, and every message your scripts printed along the way.

  YOU CLICK SEND
       │
       ▼
  Pre-request script runs    ──► console shows script messages
       │
       ▼
  Request leaves Postman     ──► console shows final URL, headers, body
       │
       ▼
  Response arrives           ──► console shows status, headers, body
       │
       ▼
  Post-response script runs  ──► console shows test messages and errors

Open the Console

Click Console in the bottom-left bar of the Postman window. A panel opens and lists each request as a row. You can also open a separate window through the View menu and the Show Postman Console option.

• Click a request row to expand its details.
• Use the search box to filter rows by URL or text.
• Click the clear icon to remove old entries.
• Switch on Show logs to see script messages next to the requests.

What the Console Reveals

Console Detail	Problem It Solves
Final request URL	Shows whether variables resolved correctly
Request headers	Shows added headers such as Authorization and Content-Type
Request body	Confirms the exact data sent
Redirect chain	Reveals hidden redirects between servers
Response headers and body	Shows raw data before any formatting
Timing details	Explains where the delay occurred

Print Messages from Scripts

The console object works inside both pre-request and post-response scripts.

console.log("Plain message");
console.info("Information message");
console.warn("Warning message");
console.error("Error message");

const data = pm.response.json();
console.log("User name:", data.name);
console.log("Full object:", data);

Messages appear in the console with color coding. Warnings show in yellow and errors in red, which makes them easy to spot in long lists.

Inspect Variables

Print variable values at the moment a script runs.

console.log("baseUrl =", pm.variables.get("baseUrl"));
console.log("token   =", pm.environment.get("token"));
console.log("userId  =", pm.collectionVariables.get("userId"));

A value of undefined means the variable does not exist in any active scope. Check the selected environment in the top-right dropdown first.

Typical Debugging Cases

Variable Not Resolved

The console shows a URL such as {{baseUrl}}/users with the braces still visible. Select the right environment or create the missing variable.

Missing Authorization Header

The request row lacks an Authorization header. Open the Authorization tab and confirm the type, or check that the request inherits auth from its parent.

Script Error

A red message such as ReferenceError: data is not defined points to a typo or a variable used outside its block. Read the message and fix the named line.

Wrong Content Type

A 415 response often comes from a missing Content-Type header. The console lists the headers that actually left Postman, so compare them with the API documentation.

A Simple Debugging Routine

1. Clear the console.
2. Send the failing request once.
3. Read the final URL, headers, and body in the console.
4. Compare them with the API documentation.
5. Add console.log lines to scripts when values look wrong.
6. Fix one thing at a time and send again.

Protect Private Data

• Remove tokens and passwords from console screenshots.
• Avoid logging secrets inside shared scripts.
• Clear the console before screen sharing.
• Delete verbose logging lines once the problem is solved.

Key Points

• The console records the real request, the raw response, and script messages.
• console.log, info, warn, and error print values from scripts.
• Unresolved braces in the final URL signal a missing variable.
• Comparing sent headers with documentation solves many 4xx errors.
• Keep secrets out of logs and screenshots.