Installing Postman & Interface Tour
With HTTP methods and status codes fresh in mind, it's time to install the tool you'll use for the rest of this track. Postman is a desktop application (also available in a browser-based lite version) that lets you build, send, and organize HTTP requests without writing any code — everything you'd otherwise do with a curl command or a bit of throwaway script, but with a proper UI, saved history, and a place to keep reusable test collections.
Downloading and Installing
- Go to postman.com/downloads and download the desktop app for your operating system (Windows, macOS, or Linux).
- Run the installer. No special configuration is needed — accept the defaults.
- On first launch, Postman will offer to have you sign in or create a free account. Signing in is optional — it enables syncing your collections and environments across devices and lets you use Postman's cloud-based workspaces, but you can skip it entirely and use Postman as a fully local, offline request builder. For learning and personal practice (like everything in this track), working locally without an account is perfectly fine.
Interface Tour: The Sidebar
The left sidebar is where everything you build gets organized, across a few tabs:
- Collections — folders of saved requests. You'll build a "RecipeBox API"
collection starting in the Postman Collections lesson, grouping requests like
GET
/recipesand POST/recipestogether. - Environments — named sets of variables (like a base URL that differs between staging and production). Covered in depth in the Environments & Variables lesson.
- History — every request you've sent, most recent first — handy for finding something you ran five minutes ago without having saved it.
Interface Tour: The Request Builder
The main tab where you build a request has, left to right along the top: a method dropdown (where you pick GET, POST, PUT, PATCH, DELETE, and others) and a URL bar where you type the endpoint, e.g. https://api.recipebox.example.com/recipes, plus a Send button.
Below that sits a row of sub-tabs that control everything about the request:
| Tab | What It's For |
|---|---|
| Params | Query string parameters, added as key/value pairs. Postman appends them to the URL automatically — e.g. adding a category param builds ?category=Dinner for you. |
| Headers | Custom HTTP headers, like an Authorization token or a specific Accept value. |
| Body | The request payload — where you write the JSON for a POST, PUT, or PATCH. |
| Auth | A dedicated place to configure authentication (Bearer token, Basic auth, API key, etc.) without hand-writing the header yourself. Covered fully in the Authentication lesson. |
| Scripts | JavaScript that runs before the request is sent (pre-request) or after the response arrives (post-response, where your assertions live). Covered in the Writing Assertions and Pre-request Scripts lessons. |
Interface Tour: The Response Panel
After you hit Send, the response appears in a panel below the request. It shows:
- Body — the response payload, pretty-printed and syntax-highlighted if it's JSON.
- Status — the numeric status code (e.g. 200 OK) right next to the response time.
- Time — how long the round trip took, in milliseconds — useful for spotting a suspiciously slow endpoint.
- Size — the response size, headers included.
- Headers — a tab showing every response header the server sent back, like
Content-Type.
Saving Your Work
Any request you build can be saved with the Save button (or Ctrl+S /
Cmd+S) into a collection. Saving matters for this track specifically: starting in the
next lesson you'll build up a whole "RecipeBox API" collection of requests, and later lessons
(Collections, Environments, Collection Runner, Newman) all assume you've been saving as you go
rather than starting from a blank, unsaved tab each time.