Installing Postman and Navigating the Interface

This is a hands-on companion to the API Testing Masterclass. You already know what HTTP methods, status codes, and JSON bodies are — this course teaches you to drive them through Postman, the most widely-used GUI for API testing. The first job is to get the tool installed and learn to read its interface fluently. Once you can find your way around, every later lesson is just clicking the right buttons.

Installing Postman

Postman ships in two flavours and you'll mostly use the first:

Desktop app — available for Windows, macOS, and Linux. Download from postman.com/downloads. This is the version you want for serious work: it can hit localhost, run collections offline, and integrates with Newman.
Web version — go.postman.co runs in a browser, but to send requests it needs a small helper called the Postman Agent installed locally. The agent proxies requests so the browser can reach localhost and bypass CORS.

Sign-in is optional but useful. You can click "Skip and go to the app" the first time you launch Postman — every feature in this course works without an account. Signing in (free tier is fine) unlocks cloud sync, team workspaces, and the ability to share collections by link.

If you're on Linux, the Snap package or the official .tar.gz both work; on macOS, Homebrew Cask (brew install --cask postman) is the cleanest install. Make sure your version is at least v10 — older majors are missing the modern Collections sidebar and Auth helpers we'll use throughout.

The Postman interface, area by area

When you launch the app, the window splits into four zones. Learning to name each one is half the battle when a tutorial says "open the Auth tab" and you're not sure where to look.

Postman interface — areas you'll use every day

	What's there	When you'll use it
Sidebar	Collections, Environments, History, APIs, Mock Servers — left edge of the window	Open or save requests, switch between dev/staging/prod environments, replay history
Request builder	Method dropdown, URL bar, and tabs: Params, Authorization, Headers, Body, Pre-request Script, Tests	Build the request — choose verb, type the URL, set body and auth, write tests
Response panel	Status code, time, size, and tabs: Body (Pretty/Raw/Preview), Cookies, Headers, Test Results	Read what the server returned and check whether your assertions passed
Bottom bar	Console toggle, Runner, Trash, sync indicator	Open the Console (Ctrl/Cmd+Alt+C) for low-level debugging; launch the Runner for full collections

A short tour of each:

Sidebar. Collections at the top — every saved request lives in one. Below it, Environments (dev, staging, prod), History (every request you've sent in this workspace), and APIs (OpenAPI specs). Treat the sidebar as your filing cabinet.
Request builder. The big middle section. The method dropdown (GET, POST, PUT…) sits to the left of the URL bar. Below the URL is a row of tabs — Params, Authorization, Headers, Body, Pre-request Script, Tests. Each tab opens a panel. We'll spend lots of time in Body and Tests.
Response panel. Appears under the request builder once you click Send. Status code on the left (200 OK in a green pill), then time, size, and a Save Response dropdown. Tabs: Body, Cookies, Headers, Test Results. The Body tab has its own toggle — Pretty | Raw | Preview — for choosing how to render the response.
Top bar. Workspace switcher on the left ("My Workspace" by default), New and Import buttons next to it, environment selector and the eye icon (quick-view variables) on the right.
Bottom bar. A console icon ("Console") opens the Postman Console, the single most useful debugging tool in the app. The Runner button next to it launches Collection Runner.

Creating your first request

To open a fresh tab: click the + button on the tabs row, or press Cmd/Ctrl+T. Alternatively use the New button in the top-left → HTTP Request. You'll get an untitled tab with method GET and an empty URL. That's your starting point for the next lesson.

The Postman Console — your best debugging friend

Open it via View → Show Postman Console or Ctrl/Cmd+Alt+C. The console logs every request and response with the actual bytes Postman put on the wire — including the resolved URL after variable substitution, the final headers, and any console.log() from your test scripts. Whenever something behaves weirdly ("but I set the variable!"), the console is where you go.

Postman vs Postman Agent

A common confusion: the desktop app is not the same thing as the agent.

Desktop app — full Postman, runs requests directly from your machine.
Postman Agent — a tiny helper installed alongside the desktop or web version that lets the web version reach localhost and self-signed certs.

If you're using the desktop app (recommended for this course), you don't need to think about the agent at all.

Settings worth changing today

Settings → General → Automatically follow redirects — leave on (default). Most APIs use 301/302 freely.
Settings → General → SSL certificate verification — turn off for test environments with self-signed certs, or you'll get cryptic TLS errors. Leave on for production targets.
Settings → Themes → Dark/Light — purely cosmetic; pick whichever doesn't tire your eyes.
Settings → Shortcuts — the shortcut list. The two to memorise: Cmd/Ctrl+S saves a request, Cmd/Ctrl+Enter sends it.

⚠️ Common mistakes

Using the web version without installing the agent. The web app silently fails on localhost URLs because the browser can't reach them. Either install the agent or just use the desktop app — for a course, the desktop app is the simpler answer.
Working without a workspace. Every request you save lives in a workspace. New users sometimes save into "My Workspace" forever, then get confused when teammates can't see anything. Create a workspace for this course (e.g. "Postman Course Practice") so your work is contained.
Ignoring the Postman Console. Newcomers debug by re-reading their request and guessing. The console shows the resolved request — a 30-second look there saves an hour of "but my URL looks right."

🎯 Practice task

Get oriented. 15-20 minutes.

Install the Postman desktop app from postman.com/downloads. Open it and either sign in (free) or click Skip and go to the app.
Create a new workspace: top-left workspace dropdown → Create Workspace → name it "Postman Course". Set visibility to Personal.
Open a new request tab (Cmd/Ctrl+T). Type https://jsonplaceholder.typicode.com/users in the URL bar. Don't send it yet.
Click each tab in the request builder — Params, Authorization, Headers, Body, Pre-request Script, Tests. Read what's in each panel. Don't memorise; just notice where things live.
Open the Postman Console (Cmd/Ctrl+Alt+C). Leave it open in a second window for the rest of this course.
Click Send. The response panel appears below — find the status code, the time, and the size. Click between Pretty, Raw, and Preview on the Body tab. Switch to the Headers tab and read the response headers.
Stretch: open Settings → General and skim every option. You don't need to change anything; just know what's there for when something behaves oddly later.

You can now find every important control in the Postman window. The next lesson teaches you to actually drive a GET request with confidence — including path parameters, query parameters, and how to save the result to a collection.