English for Postman Developers
Vocabulary for developers using Postman — collections, environments, pre-request scripts, and mock servers — for teams discussing API testing workflows in English.
Postman conversations tend to move fast in Slack — “can you send me the collection,” “which environment are you hitting” — and the vocabulary is small but easy to use loosely. Being precise about it saves a round trip of “wait, which endpoint did you actually mean.”
Organizing Requests
Collection — a saved, shareable group of related API requests, often organized to mirror an API’s structure (auth, users, billing, etc.).
“Don’t keep this request loose in your workspace — add it to the shared collection so the rest of the team can reuse it.”
Environment — a named set of variables (base URL, API key, tokens) that a collection’s requests reference, letting the same requests run against dev, staging, or production by switching one dropdown.
“You’re hitting production — switch your environment to staging before you run that delete request again.”
Folder — a way of grouping related requests within a collection, often used to represent a resource or a user flow.
“Move the auth requests into their own folder — right now they’re mixed in with billing requests and it’s hard to find anything.”
Scripting and Automation
Pre-request script — JavaScript that runs before a request is sent, commonly used to generate a token, compute a signature, or set a dynamic variable.
“Add a pre-request script to refresh the auth token automatically — we shouldn’t be pasting a fresh token into the environment every twenty minutes.”
Test script — JavaScript that runs after a response comes back, used to assert on status codes, response shape, or specific field values.
“The test script checks that
status === 200and that the response has auserIdfield — if either fails, the run shows red.”
Collection runner — a feature that executes every request in a collection (or folder) in sequence, often used for quick regression checks or as a lightweight CI substitute.
“Run this through the collection runner before you demo it — it’ll catch anything that broke since the last time you touched this flow.”
Simulating APIs
Mock server — a Postman feature that returns example responses defined in the collection without hitting a real backend, letting frontend work proceed before the API exists.
“Point the frontend at the mock server for now — the real endpoint isn’t built yet, but the response shape is locked in.”
Chained requests / variable extraction — capturing a value from one response (like an ID or token) and saving it as a variable for use in a subsequent request, avoiding manual copy-paste between requests.
“Extract the orderId from the create-order response into a variable so the next request in the flow picks it up automatically.”
Common Mistakes
- Sharing a screenshot of a single request instead of exporting or sharing the collection, which loses the environment variables and script context.
- Running a “delete” or “reset” request against production because the environment dropdown wasn’t checked first.
- Hardcoding a token directly into a request URL instead of using an environment variable, so it silently goes stale or leaks into shared collections.
Practice Exercise
- Explain, in two sentences, the difference between a collection and an environment to someone new to Postman.
- Write a short Slack message asking a teammate to double-check their environment before running a destructive request.
- Draft a message explaining why a pre-request script for token refresh is better than manually pasting a token.