Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 30 ยท Getting Started

Installing Postman and a tour of the interface

Install Postman, choose between the desktop and web app, and learn the workspace, sidebar, tabs, request builder, response viewer and console.

Postman is a graphical application for building HTTP requests, sending them and inspecting the answers. Before you can use it you need to install it (or open it in a browser) and learn where the main controls live. Once you know the layout, the rest of this tutorial becomes a matter of using the same few screens in more and more powerful ways.

A website cannot run a desktop application, so this lesson is a guided walkthrough you follow on your own computer. The steps and descriptions here are read-only text. The runnable examples are stand-ins: small JavaScript programs that model what a Postman request is underneath (a plain data object) and how it turns into the text that goes over the wire. That understanding helps whenever a screen looks confusing.

Postman updates often, and menus, tab names and layouts move between versions. Use this lesson as a map of the ideas, and expect small differences in labels. If a control is not where you expect, look for its name in the nearby tabs or use the search box.

Desktop app or web app?

Postman is available in two forms:

  • The desktop app for Windows, macOS and Linux. You download an installer from the official Postman website and run it. This is the usual choice for daily work, because it can send requests to servers running on your own computer (localhost) and has the full feature set.
  • The web app, which runs in your browser after you sign in. It needs no installation. A browser cannot freely send arbitrary requests to other sites or to your local machine, so the web version typically relies on a small helper called the Postman Agent for requests that a browser would block, such as calls to localhost.

If you want to follow along with a server you run yourself, install the desktop app. If you only want to try public APIs quickly, the web app is enough.

Pick your Postman

Desktop app Install once. Works with localhost.
Web app Nothing to install. Needs a sign-in.
Newman A command-line runner for automation.

Newman comes later, in the CI lesson.

1 / 2

Installing Postman

The steps below are the usual path. Always download from the official Postman website, and be careful with unofficial mirrors.

  1. Open the official Postman download page and choose your operating system.
  2. Run the installer (on Windows an .exe, on macOS a disk image you drag into Applications, on Linux a package or archive).
  3. Start Postman. It asks you to sign in or create an account. Postman has a free plan that is enough for everything in this tutorial. Some versions offer a limited mode without an account, but accounts unlock saving, syncing and collaboration.
  4. After signing in, you land in your workspace.

Never paste real production passwords or secret keys into a shared workspace or a public collection. Anything you sync to the cloud may be visible to teammates, and anything in a public workspace is visible to the world. Later lessons show how to keep secrets in environment variables.

Workspaces

A workspace is a container for your work: collections, environments, and other items. You can switch workspaces from the menu at the top of the window.

  • A personal workspace is only for you.
  • A team workspace is shared with colleagues, so everyone sees the same collections.
  • A public workspace is visible to anyone on the internet.

Start with your personal workspace. Moving to shared workspaces matters when you collaborate, which is covered in Postman Flows, collaboration and AI features.

The main window, area by area

The four areas to know

Sidebar Collections, environments, history.
Request builder Method, URL, params, headers, body.
Response viewer Status, time, size and body.
Console Every request and log message.
1 / 2

The sidebar runs down the left side. It lists Collections (folders of saved requests), Environments (sets of variables such as a base URL), and History (everything you sent recently, even if you did not save it). Depending on your version, other items appear here too, such as mock servers, monitors and flows.

Tabs run along the top of the main area. Each open request gets its own tab, like pages in a browser, so you can keep several requests open. A dot or similar marker on a tab means unsaved changes. Opening a new empty tab is the quickest way to start a throwaway request.

The request builder is the heart of the app. Along its top you choose the method from a drop-down, type the URL, and press Send (the keyboard shortcut is usually Ctrl+Enter, or Cmd+Enter on a Mac). Below that sit the request's tabs:

  • Params for query string parameters, in a table of keys and values with a checkbox per row.
  • Authorization for credentials. Authentication: API keys, Basic, Bearer and OAuth 2.0 covers it in detail.
  • Headers for request headers, again a table with checkboxes.
  • Body for the data you send, with several formats (raw, form-data and others).
  • Scripts for code that runs before a request is sent or after the response arrives. In older versions these were called Pre-request Script and Tests.
  • Settings for per-request options such as following redirects.

The response viewer appears below the builder after you send. At the top it shows the status code, the time the request took and the size of the response. Its tabs show the Body, Cookies, Headers and Test Results. The Body tab has views called Pretty (formatted and coloured), Raw (exactly the bytes received) and Preview (rendered, useful for HTML). You will use all of them in Your first request.

The console is a separate panel that logs every request Postman sends, with its full headers and bodies, plus anything your scripts print with console.log. Open it from the status bar at the bottom of the window or from the View menu. When a request behaves strangely, the console shows what was actually sent, which is often different from what you think you configured.

What a request is underneath

Behind the friendly screens, a Postman request is just structured data: a method, a URL, a table of params, a table of headers and a body. When you press Send, the app turns that data into the real URL and the real HTTP text. Collections are saved as JSON that stores exactly this data, which is why you can export and share them.

The stand-in below models the params table. Each row has a checkbox, just like in Postman, and only enabled rows are added to the URL.

JS A request as data: the params table

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice that the space in buy milk is encoded as %20. Postman encodes special characters in the URL for you, so you can type readable values in the table.

From request data to the HTTP text

The second stand-in goes one step further. It turns the same kind of request object into the plain-text HTTP message a server receives, and it records a console-style log line. The tool adds a few headers automatically (such as Host, and a Content-Length when there is a body), exactly as Postman does. The header values for the client name here are invented for the demo.

JS Turning a request object into the HTTP text

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Compare the output with what you see in the Postman console after sending a real request: the request line, the headers (including ones you never typed) and the body appear in the same order. The disabled header never leaves your machine, because a Postman row only counts when its checkbox is ticked.

A first-run checklist

When you open Postman for the first time, work through this checklist on your own computer:

  1. Sign in and find your personal workspace.
  2. Open a new tab with the + button.
  3. Pick GET from the method drop-down and type a URL.
  4. Open the Params and Headers tabs and look at the empty tables.
  5. Open the Console from the bottom bar and keep it visible.
  6. Find the Collections and History items in the sidebar.

You will not send anything yet. That is the next lesson.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why might you install the desktop app instead of using the web app?

    Browsers restrict requests to localhost and other sites, so the web app relies on a helper (the Postman Agent). The desktop app handles local servers directly.
  2. 2. In the Params tab, what does an unticked checkbox on a row do?

    A disabled row stays in the table so you can switch it back on later, but it is not added to the request.
  3. 3. Which Body view shows the response exactly as received, without formatting?

    Pretty formats the text for reading, Preview renders it (useful for HTML), and Raw shows the unformatted bytes as text.
  4. 4. Where would you look to see the headers Postman actually sent, including automatic ones?

    The console logs each request with its real headers and body, including headers the app added for you.

Summary

  • Postman comes as a desktop app (best for local servers) and a web app (no install, needs a helper for localhost).
  • Download only from the official site, and keep secrets out of shared or public workspaces.
  • A workspace holds your collections and environments; personal, team and public workspaces differ in who can see them.
  • The main window has a sidebar, tabs, a request builder, a response viewer and a console.
  • A request is just data (method, URL, params, headers, body) that the app turns into HTTP text when you press Send.
  • Unticked rows in the Params and Headers tables are not sent.
  • The walkthrough here is read-only, and the runnable examples are stand-ins that model the idea in JavaScript.

Next: Your first request.