Your First Postman Request

Build the mental model

Testing an API by hand always comes down to the same few moves: build a request, send it, and read what comes back. The prerequisite course showed you how with curl. Postman does the same job through a visual interface — one API client among several, not a replacement for understanding HTTP itself.

A Postman workflow starts with a new request. You choose the HTTP method, type the full URL, and add anything the endpoint expects: query parameters, custom headers, or a JSON body. None of that is unique to Postman — it's the same information curl needs, organized into fields instead of command-line flags.

Sending the request is a single action. Postman fires it over the network exactly like curl or a browser would, then lays the response out: the status code at the top, headers in one tab, and the body — usually JSON — in another.

That three-part habit — status, headers, body — is what matters. Status tells you success or failure first. Headers describe the response itself. The body is the actual data or error. Postman just gives you a faster way to see all three.

POSTMAN REQUEST WORKFLOW
------------------------
CREATE REQUEST
      |
      v
CHOOSE METHOD  (GET, POST, PUT, DELETE, ...)
      |
      v
ENTER URL      (https://api.example.com/users/42)
      |
      v
SEND
      |
      v
INSPECT RESPONSE
   +-- STATUS CODE   (200, 404, 500, ...)
   +-- HEADERS       (content-type, rate limits, ...)
   +-- BODY          (JSON data or error message)

Connect it to a real scenario

Say you want to confirm a public API returns the right fields for a user record. You create a GET request, paste the endpoint URL, and hit send. The response panel shows 200, a JSON content-type header, and a body with the expected fields.

Now suppose the endpoint requires an API key. You add it as a header the same way you would with curl's -H flag, then send again. A 401 instead of 200 tells you something is wrong before you even open the body.

• Postman is one API client among several — the same request/response model curl already taught you, shown visually.
• A Postman workflow is: create request, choose method, enter URL, send, then inspect status, headers, and body.
• Always check status, headers, and body together — a 200 with a wrong or empty body is still a bug.

Try the working example

// Illustrative only — this is NOT executed here. It represents what
// you would configure in Postman's request builder, and what the
// response panel would show back after clicking Send.

const request = {
  method: "GET",
  url: "https://api.example.com/users/42",
  headers: {
    Authorization: "Bearer <token>",
  },
};

// After Send, the response panel would display something like this:
const response = {
  status: 200,
  statusText: "OK",
  headers: {
    "content-type": "application/json",
    "x-ratelimit-remaining": "59",
  },
  body: {
    id: 42,
    name: "Aye Aye",
    email: "aye@example.com",
  },
};

This code is not run — it illustrates shape, not real execution. In the actual Postman window, the response panel would show "200 OK" at the top, a Headers tab listing content-type and rate-limit fields, and a Body tab with the formatted JSON shown above, syntax-highlighted and easy to scan.

Postman Docs — Send Requests — API Integration & Webhooks