Postman Workspaces & Collections
Postman’s Workspaces & Collections are the collaboration moat — Collections (the runnable, shareable core unit), Workspaces (shared, real-time spaces with roles), and the public API Network for discovery. One source of truth vs scattered copies. India-origin (Bangalore, 2014).
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
The Postman platform family
This page covers Postman Workspaces & Collections — the collaboration moat. The rest of the Postman platform:
Quick facts
30-second orientation- Product
- Postman Workspaces & Collections — the collaboration moat
- Vendor
- Postman (founded 2014 · Bangalore → HQ San Francisco)
- The category
- API collaboration & discovery (the platform's moat)
- Collections
- Runnable, shareable, documentable request groups — the core unit
- Workspaces
- Personal, team, partner & public shared spaces
- Public API Network
- One of the largest public API hubs (Stripe, Twilio…)
- Why it wins
- Network effects — one source of truth vs scattered copies
- Scale
- Tens of millions of devs · 500K+ companies (their figure)
- Vs
- Insomnia, Bruno, SwaggerHub, Apidog, Git-based sharing
- In India via
- TechBag — scoping, licensing, local support, GST
Understand workspaces & collections before you buy
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
What are Workspaces & Collections?
Collections are the core unit — organised, runnable, shareable, documentable groups of requests. Workspaces are the shared spaces that hold them (personal/team/partner/public), with the public API Network for discovery — Postman’s collaboration moat.
Emailed exports & scattered copies vs Postman workspaces — the honest table
What consolidation actually replaces, dimension by dimension.
| Dimension | Unprotected / signature email | Workspaces & Collections (Postman) |
|---|---|---|
| Sharing API work | Email collection exports | Workspaces (live, shared) |
| Source of truth | Scattered, divergent copies | One shared workspace |
| The unit | Ad-hoc, personal calls | Collections (runnable, shareable) |
| Access control | All-or-nothing | Roles & permissions (RBAC) |
| Onboarding | Recreate everything | Add to the workspace |
| Discovery | Hunt for third-party docs | Public API Network in-app |
| Docs | Separate, stale | Auto-generated, in sync |
| Best fit | (varies) | Any team collaborating on APIs |
Postman’s Workspaces & Collections are the collaboration moat — Collections (the runnable, shareable, documentable core unit), Workspaces (personal/team/partner/public shared spaces with roles & real-time collaboration — one source of truth vs scattered copies), and the public API Network (one of the largest public API hubs, where Stripe, Twilio & thousands publish). India-origin (Bangalore, 2014). Honest: Free is now one user with no team & it’s cloud-first — want open-source/offline/Git-based sharing? Bruno. Lighter? Insomnia. TechBag scopes the plan & adds INR/GST support.
The five pieces of the platform
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Collections
A Collection is an ordered group of API requests, the core unit of Postman, that you can run, share, document, version and automate as a reusable asset.
Workspaces
A Workspace holds a team’s collections, environments, APIs, mocks and docs together (personal, team, partner or public), as one source of truth.
Roles & real-time
Workspaces have roles (viewer, editor, admin) and real-time collaboration, so the right people see, edit or govern, with no emailed collections.
The public API Network
The public API Network is one of the largest public API hubs, where Stripe, Twilio, PayPal, Salesforce and thousands more publish APIs to try in Postman.
Network effects
The more teams and APIs on Postman, the more valuable it becomes: shared collections and a public directory create gravity scattered files can’t match.
One shared workspace for a team’s collections and environments — roles, real-time edits and the public API Network.
Twelve capabilities. Organise, collaborate, discover.
Postman lets a team organise API work into collections, collaborate in shared workspaces & discover the world’s APIs on the public Network — the collaboration moat of the Postman portfolio.
Collections — the core unit
Save requests into Collections, ordered, runnable groups you can share, document and automate as a reusable asset.
Folders, order & structure
Folders and ordering group related requests and sequence a flow, so large collections stay navigable as they grow.
Environments & variables
Keep environments (dev/staging/prod) and variables in the workspace, so the team’s collections run anywhere without hard-coded keys.
Versioning & history
Collections carry versioning and change history, so you see what changed, roll back, and keep one current source of truth.
Workspaces — personal, team, partner, public
Workspaces hold a team’s collections, environments, APIs and docs (personal, team, partner or public) in one place.
Roles & permissions (RBAC)
Roles and permissions (viewer, editor, admin) govern who can see, edit or administer, so collaboration stays controlled.
Real-time collaboration
Changes to shared collections and workspaces are live, so the team sees the current state with no exports to reconcile.
Share — team, partners, customers
Share collections with partners or customers via workspaces or links, so integration is smooth and onboarding is instant.
Auto-generated documentation
Collections generate live API documentation that stays in sync with the requests and can be shared.
The public API Network
One of the largest public API hubs, where Stripe, Twilio, PayPal, Salesforce and thousands more publish APIs to try in Postman.
Publish to the Network
Publish your public API to the Network with a workspace, collection and docs, so partners and developers discover and try it.
Fork, watch & try in-app
Fork a published collection, watch it for changes and try requests in-app, so integrating starts from a working example.
Watch Postman in action
The overview, getting started, and the core workflows.
Exploring Postbot | Postman Level Up
AI across the platform.
Learn Postman for API Testing (Step-by-Step)
Collections & workspaces in practice.
API Testing Using Postman Full Course in 5 hours
A deep, end-to-end walk-through.
Want a live, India-context walkthrough for your environment?
Book a guided demo →Shipping code is the goal. One flow gets you there.
Here’s what genuinely sets Postman apart (and when an alternative fits).
Collections — the core unit that turns ad-hoc calls into a shareable asset
On their own, API calls are stuck in one person’s history. A Collection groups and orders requests, runs anywhere with environments and variables, executes as a sequence in the Runner or Newman, shares via a workspace or link, and generates live docs, so ad-hoc calls become a reusable team asset.
Workspaces — the collaboration moat, one source of truth vs scattered copies
Emailing collection exports means diverging copies and slow onboarding. A Workspace keeps a team’s collections, environments, APIs, mocks and docs in one place, scoped as personal, team, partner or public, with viewer, editor and admin roles and live changes everyone sees.
The public API Network — discovery, and where the world's APIs are published
Integrating a third-party API used to mean hunting for docs and hand-building requests. On the public API Network, companies such as Stripe, Twilio, PayPal and Salesforce publish collections and docs, so you fork one and send a working call in Postman, and can publish your own API there.
Network effects — why collaboration & discovery is where API work lives
Postman’s moat is network effects. Shared collections accumulate a team’s API knowledge, so leaving means recreating it; more companies publishing on the API Network draws more developers; and with tens of millions already knowing Postman, new hires and partners are productive at once.
India-origin — and TechBag adds local licensing & support
Postman was founded in 2014 in Bangalore by Abhinav Asthana, Ankit Sobti and Abhijit Kane, and now has HQ in San Francisco with major R&D in Bangalore. A 2021 round valued it at $5.6B, which is historical. It bills in USD; TechBag adds plan scoping, licensing and INR/GST invoicing.
The honest scope
Collections, Workspaces and the API Network are Postman’s collaboration moat. Since March 2026 the Free plan is one user, so a shared workspace needs Team at $19 per user a month. It is cloud-centric; Bruno offers open-source, offline, Git-based sharing, and Insomnia and Hoppscotch are lighter.
The numbers behind the platform
What your Postman journey looks like
Scoping (& the plan)
Pick a plan (Free, Solo, Team or Enterprise); Free is now one user. TechBag compares Bruno, Insomnia and Git-based sharing.
Organise into collections
Turn ad-hoc calls into Collections with folders, environments (dev/staging/prod) and variables, a reusable, documentable unit.
Collaborate in workspaces
Move collections into shared Workspaces, set roles and permissions, and collaborate in real time, not via emailed copies.
Discover & publish on the Network
Discover, fork and try APIs on the public API Network, and publish your own. TechBag supports you locally (GST).
The review scoreboard
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
Quick poll — what’s driving your evaluation?
Talk to an advisor“Our API work lives in Workspaces, one source of truth with no emailed exports. A new dev is productive on day one.”
“Collections turned our ad-hoc calls into an organised, documented, versioned asset, and we run them in CI with Newman.”
“When we integrate Stripe or Twilio, we fork their published collection and have a working call in seconds.”
“Roles give our partners exactly the workspace scope they should have, nothing more, and everyone sees changes live.”
“Losing free team sharing stung, and we evaluated Bruno for Git-based, offline sharing, but workspaces and the Network kept us.”
“We’re proud Postman started in Bangalore. TechBag scoped the right plan, handled procurement and GST, and advised honestly on tiers.”
“Docs auto-generated from the collection stay in sync with the requests, so handing off APIs to partners got far easier.”
“Postman bills in USD; TechBag added INR/GST invoicing, plan scoping for our team size, and a local contact.”
Where everyone sits — the grids
Analyst firms bury this view behind paywalls, and review-site grids score satisfaction, not fit for your estate. So here’s TechBag’s synthesis of the API-collaboration & discovery market — tap any vendor to see why it sits where it does.
TechBag Developer-Tools Grid
Execution strength vs product vision — the classic market map, minus the paywall.
The collaboration & discovery moat. This page's product.
Workflow Depth × Collaboration & Discovery
The grid nobody publishes — developer-workflow & automation depth vs collaboration depth & discovery network.
Deepest collaboration + public Network + ecosystem.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Postman vs the API-collaboration field
Insomnia, Bruno, SwaggerHub, Apidog and Git-based sharing — honest lanes; the edge is the deepest workspace collaboration + Collections + the public API Network. Want open-source/offline/Git-based sharing? Bruno. Lighter client? Insomnia. Design-first? SwaggerHub. We say so.
| Dimension | Postman | Insomnia | Bruno | SwaggerHub | Apidog | Git-based sharing |
|---|---|---|---|---|---|---|
| Position | Collaboration moat + public Network | Lighter client with team features | Open-source, offline, Git-friendly | Design-first (OpenAPI) collaboration | All-in-one (design+test) challenger | Collections in Git alongside code |
| Collections (the unit) | The core, richest unit | Collections/folders | Files-on-disk collections | Design definitions (not runnable groups) | Collections + cases | Whatever your files hold |
| Workspaces & real-time collab | Personal/team/partner/public + real-time | Team features | Git sharing (no live workspace) | Design collaboration | Team features | PRs/branches, not live |
| Public API discovery Network | One of the largest public hubs | None comparable | None | SwaggerHub registry | None comparable | None |
| Open-source / offline / Git | Cloud-first (Scratch Pad retired) | Partly open, more offline | Open-source, offline, Git-native | SaaS | Offline option | Fully Git/offline by definition |
| Roles / governance (RBAC) | Roles, RBAC, enterprise governance | Team roles (via Kong) | Via Git permissions | Design governance | Team roles | Repo permissions |
| Ecosystem / ubiquity | Tens of millions of devs | Large | Fast-rising | Established (design) | Growing | Git is universal |
| Best fit | Deepest collaboration + public discovery Network | A lighter client with team features | Open-source, offline, Git-friendly sharing | Design-first (OpenAPI) collaboration | All-in-one design+test challenger | Keep collections in Git alongside code |
Which developer-platform approach fits you?
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Choose Postman if…
- ✓You want the deepest COLLABORATION — Workspaces (personal/team/partner/public) with roles & real-time, one source of truth vs scattered copies
- ✓You want Collections — the core, runnable, shareable, documentable unit that turns ad-hoc calls into a team asset
- ✓You value DISCOVERY — the public API Network, one of the largest hubs, to find, try & publish the world's APIs
- ✓You want network effects & ubiquity — to work where tens of millions of developers and the world's APIs already are
Bruno if…
- ✓You want open-source, offline-first, Git-friendly sharing — exactly the cloud/offline concern some have with Postman
Insomnia if…
- ✓You want a lighter, well-liked client with team features (via Kong) rather than the full collaboration platform
SwaggerHub / Stoplight if…
- ✓You want a design-first (OpenAPI) collaboration/documentation specialist rather than a client-led collaboration platform
Git-based sharing / Apidog if…
- ✓You want collections versioned in Git alongside code (Bruno-style), or an all-in-one design+test challenger (Apidog)
What could this save you?
Drag the sliders (developers; hour cost as loaded rate). Estimates contrast fragmented collaboration (emailed collection exports, divergent copies, hunting for third-party docs, re-onboarding) vs Postman (shared workspaces as one source of truth, reusable collections, roles, and the public API Network for discovery) — the wins are developer time saved, consistency and faster integration. NB: illustrative — TechBag scopes the plan for your team.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Three ways to consume it
Since March 2026 Postman’s plans are Free (one user — it can no longer create a team), Solo ($9 a month, one user) and Team ($19 per user a month) — both billed annually, in USD — plus Enterprise, priced by Postman sales. Shared workspaces start at Team; Enterprise adds private and partner workspaces at scale, the Private API Network, SCIM and advanced RBAC. TechBag scopes the right plan for your team size (mindful of the free-tier changes) and handles INR/GST — and tells you honestly when a lighter or Git-based alternative (Bruno/Insomnia) fits.
Postman plans
Best for teams collaborating on APIs
- Free $0 (1 user) · Solo $9/mo · Team $19/user/mo (billed annually) · Enterprise: quote
- Collections (the core unit) + Workspaces (one source of truth) + roles/RBAC
- The public API Network — discover, try & publish the world’s APIs
+ Platform add-ons
Best for a broader rollout
- Scoped to your estate
- Add-on modules as needed
- Phased, right-sized deployment
+ scoping & local support
Best value with TechBag
- Honest plan scoping (mindful of the free-tier changes) + Bruno/Insomnia advice
- Postman bills USD, global support
- TechBag adds procurement, INR/GST invoicing & local support
Buy it for less — TechBag pricing beats list
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Get an India-ready quote
Tell us your requirements and current tools — we’ll model it against what you spend today.
The 8 questions to ask every vendor
Take this into your next vendor call — including ours.
Does more than one person touch your APIs? Would shared workspaces with roles give you one source of truth?
Need a reusable, shareable, runnable unit for your API work? Collections turn ad-hoc calls into a documented, versioned asset.
Do you integrate third-party APIs or publish your own on the public API Network?
Do you need to control who can view, edit or administer, with RBAC and enterprise governance on Enterprise?
Since March 2026: Free (1 user, cannot create a team), Solo, Team, Enterprise — TechBag scopes the right plan.
Need offline/open-source/Git-based sharing/data-residency? Weigh Bruno/Insomnia/Hoppscotch — TechBag advises honestly.
Is pure API design/documentation collaboration your focus? SwaggerHub/Stoplight are specialists — we'll say so.
Postman bills in USD (global) — TechBag adds local plan-scoping, procurement, INR/GST and support.
Questions buyers ask
Ready to collaborate on APIs in Postman?
Scope Postman (Workspaces & Collections — the collaboration moat: shared, real-time spaces with roles, the runnable/shareable Collection unit, and the public API Network for discovery) — and let a TechBag advisor pick the right plan, handle procurement and GST, and advise honestly on the free-tier changes and alternatives (Bruno/Insomnia/Git-based sharing) where they fit.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.