Postman Collection Export
Export your mock APIs as Postman collections for testing, documentation, and team collaboration
What is Postman Export?
Export your entire Mock API Builder project as a Postman Collectionβa JSON file containing all your endpoints, request examples, and documentation. Import this collection into Postman, Insomnia, or other API clients for easy testing.
Test all endpoints in Postman without manually creating each request
Share collections with teammates so everyone has the same API setup
Endpoints are organized by resource with proper folder hierarchy
Includes base URLs, headers, and example request bodies automatically
How to Export Your Project
Open Your Project
Navigate to the project you want to export from your dashboard
Go to Project Settings
Click the "Settings" tab in the project navigation
Find Export Section
Scroll to the "Export" section in settings
Click "Export to Postman"
Click the button to download the collection JSON file
Save the File
File is saved as project-name-postman-collection.json
Importing into Postman
1. Open Postman
Launch the Postman desktop app or web version
2. Click "Import"
Find the Import button in the top left corner of Postman
3. Select File or Drag & Drop
Either drag the JSON file into the import dialog, or click "Upload Files" to browse
project-name-postman-collection.json4. Confirm Import
Review the collection details and click "Import"
5. Start Testing
Your collection appears in the sidebarβclick any request to test it
π‘ Quick Import Alternative
You can also import by clicking the Import button and pasting the direct URL to your exported collection if it's hosted online.
Collection Structure
Folder Organization
Endpoints are grouped by resource type:
- β’ Users folder (GET all, GET by ID, POST, PUT, DELETE)
- β’ Products folder (all CRUD operations)
- β’ Posts folder (all CRUD operations)
- β’ And folders for each resource in your project
Base URL Configuration
The collection includes a pre-configured base URL variable:
{{baseUrl}} = https://api.mockbuilder.com/your-projectRequest Examples
Each POST/PUT/PATCH request includes example request bodies with proper field types
Headers
Common headers are pre-configured:
- β’
Content-Type: application/json - β’
Authorization: Bearer {{token}}(for protected endpoints)
Using Environment Variables
Use Postman environments to easily switch between mock and production APIs:
Development Environment
baseUrl = https://api.mockbuilder.com/your-projectProduction Environment
baseUrl = https://api.yourcompany.com/v1How to Create an Environment:
- 1. Click "Environments" in the left sidebar
- 2. Click "Create Environment"
- 3. Add
baseUrlvariable with your API URL - 4. Save and select the environment from the top-right dropdown
Testing Your API
Click any request in the collection to open it, then click "Send" to test
- β’ View response body, headers, and status code
- β’ Inspect response time and size
- β’ Save responses as examples
Test all endpoints at once using the Collection Runner:
- 1. Right-click the collection
- 2. Select "Run collection"
- 3. Click "Run" to execute all requests
- 4. Review results and identify any failures
Write tests in the "Tests" tab to validate responses:
Postman can automatically generate API documentation from your collection. Click "View in web" to create a shareable documentation page.
Using with Other API Clients
Insomnia also supports Postman collections:
- 1. Open Insomnia
- 2. Create β Import from File
- 3. Select your JSON file
- 4. Choose "Postman Collection"
Import directly in VS Code:
- 1. Install Thunder Client extension
- 2. Open Collections tab
- 3. Click Menu β Import
- 4. Select your JSON file
Import into Paw:
- 1. Open Paw
- 2. File β Import
- 3. Choose Postman format
- 4. Select your JSON file
Import collections into HTTPie:
- 1. Open HTTPie
- 2. Collections β Import
- 3. Select Postman format
- 4. Browse to JSON file
Best Practices
- βRe-export after changes to keep your Postman collection in sync with updates
- βUse environments to easily switch between mock and production APIs
- βAdd tests to requests to validate API behavior automatically
- βShare collections with your team via Postman workspaces or version control
- βDocument expected responses by saving example responses in Postman
- βUse collection variables for dynamic values like IDs or tokens
- βRun collections in CI/CD using Newman (Postman's command-line tool)