How to Share Postman Collections Without Upgrading to Team Plan

TL;DR

Postman’s free tier limits collection sharing in ways that catch a lot of developers off guard. If you need to collaborate with teammates without paying $19/user/month, you have a few workarounds, but each comes with real trade-offs. Apidog’s free plan lets you share your workspace with up to 3 users, with no upgrade required.

Introduction

Postman started as a simple Chrome extension for sending HTTP requests. Over the years it grew into a full-fledged API platform, and its pricing grew along with it. Today, teams that want to share collections and collaborate in real time need a paid plan. The free tier leaves a lot of developers looking for workarounds.

If you’re running a small team, a side project, or a startup where every dollar counts, paying $19 per user per month just to share a collection feels like a lot. That’s $228 per person per year before you’ve shipped a single feature.

The good news is there are legitimate ways to share Postman collections on the free plan. None of them are as smooth as paying for the Team plan, but they work. This guide walks through each method, explains what breaks, and shows you what a genuine free alternative looks like.

What Postman’s free plan actually allows

Before looking at workarounds, it helps to understand what the free plan includes as of 2024-2025.

Postman’s free plan gives you:

• 1 user per workspace (no shared editing)
• Up to 3 active public workspaces
• Unlimited personal workspaces
• 1,000 mock server calls per month
• 1,000 monitoring calls per month
• Collection runs limited to 25 per month on the cloud runner

The critical limitation: you can’t invite teammates to a private workspace on the free plan. Private workspaces require at least the Basic plan at $19/user/month. That’s the wall most small teams hit first.

Method 1: Export the collection as JSON and share the file

The most direct workaround is exporting your collection as a JSON file and sending it to your teammate.

How to do it:

1. Open Postman and navigate to your collection in the left sidebar.
2. Click the three-dot menu next to the collection name.
3. Select “Export.”
4. Choose Collection v2.1 format (this is the current standard and has the widest compatibility).
5. Save the JSON file and share it via email, Slack, or a shared drive.

Your teammate imports it by going to File > Import and dragging in the JSON file.

What breaks:

The moment you export, the collection becomes a snapshot. If you add a new endpoint or fix a request, your teammate has no way of knowing. They’re working from a stale copy.

Environment variables don’t travel with the collection by default. You need to export environments separately, and your teammate has to import those too. If you forget one variable, their requests will fail and they’ll spend time debugging something that isn’t actually broken.

There’s no merge workflow. If two people edit their local copies simultaneously and then try to reconcile them, you’re doing it by hand.

This method works for occasional one-time handoffs. It breaks down fast when the collection is actively changing.

Method 2: Use a public workspace

Postman lets you create public workspaces on the free plan. Anyone with the link can view and fork the collection.

How to set it up:

1. Create a new workspace in Postman.
2. When prompted to choose visibility, select “Public.”
3. Add your collection to the public workspace.
4. Share the workspace URL with your teammates.

Your teammates can fork the collection to their own workspace and work from there.

What breaks:

Public means public. Anyone on the internet can find and view your collection if they have the URL or search Postman’s public API network. For internal tools, staging environments, or anything with authentication tokens baked into example responses, this is a significant risk.

Forked collections don’t stay in sync automatically. If you update the original, teammates need to manually pull changes into their fork. There’s no notification that a change happened.

Commenting and direct collaboration still require the Team plan. Public workspaces are read-only for viewers; they can’t edit the original.

This method works well for open-source projects or public API documentation. It’s not right for internal team workflows.

Method 3: Use a Git repository as the sync layer

Some teams solve the sync problem by treating the exported JSON as a code artifact and committing it to a Git repository.

The workflow looks like this:

1. One person owns the Postman collection and exports it after every meaningful change.
2. They commit the updated JSON to a shared Git repo (GitHub, GitLab, Bitbucket).
3. Teammates pull the latest version and import it into their local Postman.

What breaks:

Every import overwrites the existing local collection. If a teammate made local changes, those changes disappear unless they exported and merged first.

The workflow requires discipline. Someone has to remember to export and commit every time something changes. In practice, the Git version almost always lags behind the actual Postman state.

You can’t run requests directly from a Git repo. Someone always has to do the import step, which takes time and creates friction.

This method is better than raw file sharing because it gives you a history and a single source of truth, but the manual steps add overhead that slows teams down.

Method 4: Use Postman’s free personal workspace with one “primary” account

Some small teams work around the collaboration limit by having everyone share one Postman account. One person logs in on multiple machines using the same credentials.

This is against Postman’s Terms of Service and creates real problems:

• Postman can detect shared credentials and lock the account.
• Changes made by one person can overwrite changes made by another if sync conflicts occur.
• There’s no way to attribute changes to specific people.

This method is mentioned here because teams do use it, not because it’s a good idea.

How Apidog handles free-tier sharing

Apidog takes a different approach to the collaboration problem. The free plan includes up to 3 team members in a shared workspace, with real-time sync across all of them. No workarounds, no JSON file shuffling.

When you make a change to an API definition in Apidog, your teammates see it immediately. You’re all working from the same source of truth without anyone having to export or import anything.

If you’re already using Postman, you can import your existing collections directly. Apidog reads Postman Collection v2.1 format, so the switch is one click, not a weekend project.

The free plan also includes:

• Full API design editor (OpenAPI 3.0 and Swagger)
• Smart Mock for generating realistic responses without a cloud dependency
• A test runner with no monthly run limits
• API documentation generated automatically from your definitions
• Local-first storage, so your data stays on your machine unless you choose to sync

For a team of 2-3 people, the Apidog free plan covers the same ground as Postman’s Team plan, at no cost.

Choosing the right method for your situation

Here’s a quick decision guide:

If your team is actively building APIs and you’re hitting Postman’s sharing limits, the JSON and Git workarounds will slow you down. They solve the immediate problem but add ongoing friction.

FAQ

Can I share a Postman collection without an account?Yes. Export the collection as a JSON file and send the file directly. The recipient can import it without a Postman account if they’re using an API client that supports Postman Collection v2.1 format, including Apidog.

Does Postman Basic plan allow team sharing?Yes. The Basic plan at $19/user/month allows private workspace collaboration with multiple users. The free plan does not.

What is a Postman public workspace?A public workspace is visible to anyone on the internet. Visitors can view and fork collections but can’t edit the originals. It’s free to create up to 3 public workspaces on the free plan.

Will my environment variables export with my collection?No. Environment variables are exported separately. Go to Environments in the sidebar, click the three-dot menu on the environment you need, and export it as a separate JSON file. Share both files with your teammate.

How many users can share a workspace on Apidog’s free plan?Apidog’s free plan supports up to 3 users in a shared workspace with real-time sync, no credit card required.

Can I import my existing Postman collections into Apidog?Yes. Apidog supports direct import of Postman Collection v2.1 JSON files. Go to Import in Apidog, select your file, and your collection comes in with requests, headers, and environment variables intact.

The sharing limitations on Postman’s free tier are real, and the workarounds have real costs in time and reliability. For teams of up to 3 people who need actual collaboration, switching to a tool built for free-tier sharing is often cleaner than patching together a workflow that requires constant manual effort.