Postman Fundamentals
Postman is an API collaboration platform. You compose HTTP and other protocol requests, group them into collections, bind them to environments, add tests, and run that work from the desktop app, the Collection Runner, or a command-line runner in CI.
itSoftware engineering | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic — Postman Fundamentals
Postman is the shared drawer where your team's API calls live when sticky notes and half-remembered curl lines stop scaling. You compose a request, send it, save it, and suddenly the same call can be documented, mocked, monitored, or run in CI without anyone reinventing the headers.
Before this shape of tool, people rebuilt method, URL, auth, and body for every attempt. The collection is the answer to that tax: a portable set of requests plus the scripts, variables, and examples that travel with them. The environment is the aiming device. Point the same collection at local, staging, or production by swapping variable values, not by editing twenty URLs by hand.
Three ideas carry most of the weight. First, everything useful hangs off the collection. Second, variable scopes nest, and the narrowest name wins, which is why the wrong active environment produces the most convincing wrong answers. Third, runners are the same work in different rooms: Collection Runner in the app, monitors on a schedule, Newman or the Postman CLI on a build agent.
The surprise that bites professionals is secrecy theater. A variable marked "secret" in the UI is still ordinary data in exports, reports, and many API reads. Local values that make the desktop glow green often never appear in the JSON Newman loads. If CI cannot see the token, it is not because Newman forgot Authorization; it is because the secret never left your laptop. Public workspaces multiply the blast radius. Treat shared collections as credential documents until proven empty.
Read the intro when you want the architecture in full sentences. Use the cheatsheet when you need scope order, script order, or runner differences under pressure. Field Notes is where the leak and local-versus-export failures sit without apology. The practice reference and exercise take you through Newman against Postman Echo so a failing assertion is a non-zero exit code, not a vibe.
You do not need to master Spec Hub, Flows, and every protocol on day one. Get one collection honest, one environment clean, and one headless run green. The rest of the platform is furniture around that spine.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://learning.postman.com/docs/introduction/overview/
Supports
- 00-novice
- 01-intro
- 06-links
- https://learning.postman.com/docs/getting-started/basics/postman-elements/
Supports
- 01-intro
- 02-slides
- 03-cheatsheet
- 05-quiz
- 07-video-script
- https://learning.postman.com/docs/sending-requests/variables/variables/
Supports
- 01-intro
- 03-cheatsheet
- 05-quiz
- 12-field-notes
- https://learning.postman.com/docs/tests-and-scripts/write-scripts/intro-to-scripts/
Supports
- 01-intro
- 03-cheatsheet
- 04-practice-reference
- 05-quiz
- https://learning.postman.com/docs/collections/running-collections/intro-to-collection-runs/
Supports
- 01-intro
- 03-cheatsheet
- 06-links
- https://learning.postman.com/docs/designing-and-developing-your-api/mocking-data/setting-up-mock/
Supports
- 01-intro
- 03-cheatsheet
- 05-quiz
- https://learning.postman.com/docs/sending-requests/authorization/authorization-types/
Supports
- 03-cheatsheet
- 06-links
- https://learning.postman.com/docs/reference/newman-cli/installing-running-newman/
Supports
- 01-intro
- 04-practice-reference
- 05-quiz
- 08-exercise
- https://learning.postman.com/docs/reference/newman-cli/command-line-integration-with-newman/
Supports
- 01-intro
- 03-cheatsheet
- 05-quiz
- 12-field-notes
- https://github.com/postmanlabs/newman
Supports
- 04-practice-reference
- 05-quiz
- https://schema.postman.com/
Supports
- 01-intro
- 06-links
- https://learning.postman.com/docs/collaborating-in-postman/using-workspaces/creating-workspaces/
Supports
- 01-intro
- 06-links
- 12-field-notes
- https://blog.postman.com/timeline-postman-journey-to-api-platform/
Supports
- 10-timeline
- 06-links
- https://blog.postman.com/how-we-built-postman-product-and-company/
Supports
- 10-timeline
- https://aws.amazon.com/blogs/startups/postman-building-an-api-collaboration-platform-for-two-million-developers/
Supports
- 10-timeline
- https://en.wikipedia.org/wiki/Postman_(software)
Supports
- 10-timeline
- https://www.cloudsek.com/blog/postman-data-leaks-the-hidden-risks-lurking-in-your-workspaces
Supports
- 12-field-notes
- https://github.com/postmanlabs/newman/issues/3070
Supports
- 05-quiz
- 12-field-notes
- https://community.postman.com/t/do-we-have-to-use-initial-variables-from-environment-variables/15796
Supports
- 05-quiz
- 12-field-notes
- https://community.postman.com/t/how-to-pass-github-secrets-to-newman-run-with-collections-and-environments/80948
Supports
- 04-practice-reference
- 05-quiz
- https://postman-echo.com/
Supports
- 08-exercise
- https://dchonch.github.io/awesome-postman/
Supports
- 09-awesome-links
