How to Share Postman Collections Without Upgrading to Team Plan

TL;DR

Postman’s free tier does not support private workspace collaboration. If you need to share collections without paying $19/user/month, you can export JSON, use a public workspace, or sync exports through Git—but each workflow has trade-offs. Apidog’s free plan supports shared workspaces for up to 3 users with no upgrade required.

Try Apidog today

💡 Apidog is a free, all-in-one API development platform for API design, testing, mocking, and documentation, with collaboration included in the free tier. No credit card required.

Introduction

Postman started as a simple Chrome extension for sending HTTP requests. It has since become a full API platform, and its pricing model has changed with it. Today, teams that need private workspace collaboration must use a paid plan.

For small teams, side projects, and early-stage startups, paying $19 per user per month just to share a collection can be hard to justify. That is $228 per person per year before you account for any other tooling.

There are still ways to share Postman collections on the free plan. They work, but they are not frictionless. This guide shows the practical options, how to use each one, what breaks, and when it makes more sense to use a free collaboration-first alternative.

What Postman’s free plan allows

Before choosing a workaround, understand the free-plan limits.

Postman’s free plan includes:

• 1 user per workspace
• Up to 3 active public workspaces
• Unlimited personal workspaces
• 1,000 mock server calls per month
• 1,000 monitoring calls per month
• Cloud collection runs limited to 25 per month

The key limitation is this:

You cannot invite teammates to a private workspace on Postman’s free plan.

Private workspace collaboration requires at least the Basic plan at $19/user/month.

Method 1: Export the collection as JSON

The simplest workaround is to export your collection and send the JSON file to your teammate.

Steps

1. Open Postman.
2. In the left sidebar, find the collection you want to share.
3. Click the three-dot menu next to the collection name.
4. Select Export.
5. Choose Collection v2.1.
6. Save the JSON file.
7. Share it through Slack, email, Git, or a shared drive.

Your teammate imports it with:

File > Import > Upload Files

or by dragging the JSON file into Postman.

What breaks

This creates a snapshot, not a shared source of truth.

If you later add a request, update headers, or fix a body payload, your teammate will not receive those changes automatically.

Environment variables are also separate. If your collection uses variables like this:

{{baseUrl}}/users/{{userId}}

you must export the environment separately:

1. Go to Environments.
2. Click the three-dot menu for the environment.
3. Select Export.
4. Share the environment JSON along with the collection JSON.

If you forget this step, your teammate’s requests may fail even though the collection itself imported correctly.

Use this when

Use JSON export when:

• You need a one-time handoff.
• The collection rarely changes.
• You do not need collaborative editing.

Avoid it for active API development.

Method 2: Use a public workspace

Postman allows public workspaces on the free plan. Anyone with access can view and fork the collection.

Steps

1. Create a new workspace in Postman.
2. Set the workspace visibility to Public.
3. Add your collection to that workspace.
4. Share the workspace URL with your teammates.

Teammates can fork the collection into their own workspace.

What breaks

Public means public.

Do not use this for internal APIs, staging endpoints, private schemas, or collections that include sensitive examples.

Watch for:

• Authorization headers
• API keys
• Bearer tokens
• Internal hostnames
• Example responses containing private data

Forks also do not stay in sync automatically. If you update the original collection, teammates need to manually pull changes into their fork.

Public workspace viewers cannot edit the original collection unless you are using a paid collaboration plan.

Use this when

Use a public workspace when:

• The API is public.
• The collection is for open-source users.
• You want public API documentation or examples.

Avoid it for private team workflows.

Method 3: Use Git as the sync layer

Another option is to treat the exported Postman collection as a versioned artifact.

Workflow

1. Export the Postman collection as JSON.
2. Commit it to a Git repository.
3. Teammates pull the latest JSON.
4. Teammates import the file into their local Postman workspace.

Example repo structure:

api/
  postman/
    collection.json
    local.environment.json
    staging.environment.json

Example commit:

git add api/postman/collection.json
git commit -m "Update user API collection"
git push origin main

Teammates then pull and import:

git pull origin main

What breaks

Git gives you history, but Postman does not become Git-native.

Problems include:

• Someone must remember to export after every meaningful change.
• Teammates must manually import the latest JSON.
• Local changes can be overwritten during import.
• JSON diffs are often noisy and hard to review.
• Merge conflicts are painful if multiple people edit the collection independently.

This is better than sending files through Slack, but it still adds manual steps.

Use this when

Use Git sync when:

• Your team already works heavily in Git.
• You need version history.
• You can enforce an export/import process.

Avoid it if your team expects real-time collaboration.

Method 4: Share one Postman account

Some teams try to bypass free-plan limits by sharing one Postman login across multiple people.

This is not recommended.

It creates several problems:

• It can violate Postman’s Terms of Service.
• Account access becomes a security risk.
• You cannot attribute changes to specific teammates.
• Sync conflicts can overwrite work.
• If the account is locked, everyone loses access.

This method exists in the wild, but it is not a reliable team workflow.

How Apidog handles free-tier sharing

Apidog approaches collaboration differently. Its free plan includes shared workspace access for up to 3 users, with real-time sync.

That means:

• No manual JSON export/import loop.
• No public workspace workaround.
• No shared account.
• No Git repo required just to keep collections in sync.

When one teammate updates an API definition, the rest of the workspace sees the change from the same source of truth.

If you already use Postman, you can import existing collections directly. Apidog supports Postman Collection v2.1 JSON imports, so migration starts with the same export file used in the workaround above.

Import a Postman collection into Apidog

1. Export your Postman collection as Collection v2.1.
2. Open Apidog.
3. Go to Import.
4. Select the Postman JSON file.
5. Import the collection into your workspace.

Apidog’s free plan also includes:

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

For teams of 2–3 developers, this avoids the most common Postman free-tier collaboration bottleneck.

Choosing the right method

Use this decision table:

Situation	Best approach
One-time handoff, collection is stable	Export JSON and share the file
Open-source project, no sensitive data	Postman public workspace
Team of developers, active development	Apidog free plan
Already on Git, want version history	Git + JSON export workflow

If your API is changing daily, JSON exports and Git sync will slow the team down. They solve sharing, but they do not solve collaboration.

FAQ

Can I share a Postman collection without an account?

Yes. Export the collection as a JSON file and send it directly. The recipient can import it into Postman or another API client that supports Postman Collection v2.1 format, including Apidog.

Does Postman Basic allow team sharing?

Yes. Postman Basic costs $19/user/month and supports private workspace collaboration with multiple users. The free plan does not.

What is a Postman public workspace?

A public workspace is visible on the internet. Visitors can view and fork collections, but they cannot edit the original collection. Postman’s free plan supports up to 3 active public workspaces.

Will my environment variables export with my collection?

No. Environment variables are exported separately.

Export them from:

Environments > three-dot menu > Export

Share both files:

collection.json
environment.json

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 and no credit card required.

Can I import existing Postman collections into Apidog?

Yes. Export your Postman collection in Collection v2.1 format, then import the JSON file into Apidog.

Final takeaway

Postman’s free-tier sharing limits are manageable for occasional handoffs, but they become expensive in active development. JSON exports, public workspaces, and Git-based sync all work, but each adds manual effort or security trade-offs.

If your team has up to 3 people and needs real collaboration, a free shared workspace in Apidog is usually cleaner than maintaining a workaround-heavy Postman workflow.