? Importing & Exporting Collections

? Quick Overview

Postman allows you to import and export collections to share APIs, back up requests, or move work between teams and systems. Collections can be shared as files, links, or via workspaces, making collaboration easy and consistent.

? Key Concepts

Collections store related API requests together
Collections can be exported as JSON files
Import supports files, links, and raw text
Shared collections maintain structure and metadata
Versioning helps track API changes

? Syntax / Theory

Postman collections use a JSON schema that defines folders, requests, headers, authorization, scripts, and variables. Exported files follow a specific version format such as Collection v2.1.

? Code Example (Collection JSON Snippet)

? View Code Example

// Sample Postman collection structure (simplified)
{
  "info": {
    "name": "User API Collection",
    "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
  },
  "item": [
    {
      "name": "Get Users",
      "request": {
        "method": "GET",
        "url": "https://api.example.com/users"
      }
    }
  ]
}

? Live Output / Explanation

When this collection is imported into Postman, it creates a folder named User API Collection with a single request called Get Users. You can run, edit, or share this collection.

? Interactive / Visual Explanation

Think of a Postman collection like a folder tree:

? Collection
├── ? Request 1
├── ? Request 2
└── ? Sub-folder → Requests

Importing recreates this structure exactly in another Postman workspace.

? Interactive Demo: The Export Flow

Simulate how the export function works in Postman below. Click the button to generate the JSON file.

? My Collections Postman Sidebar

User API Collection 3 Requests

Format: Collection v2.1 (Recommended)

✅ Export Successful!
Generating file: User_API_Collection.postman_collection.json...

// JSON Content Preview:
{ "info": { "name": "User API Collection", ... } }

? Use Cases

Sharing APIs with frontend or mobile teams
Backing up API test suites
Migrating APIs between environments
Collaborating with remote teams
Publishing public API examples

? Tips & Best Practices

Always export using the latest collection version
Name collections clearly for easy identification
Remove sensitive tokens before sharing
Use environment variables instead of hardcoding values
Keep collections modular and organized

✍️ Try It Yourself

Create a new collection in Postman
Add at least two API requests
Export the collection as a JSON file
Import it into another workspace or Postman app
Verify that all requests work correctly