Skip to content

Importing and Exporting Postman Collections in Martini

Overview

Martini allows you to both import and export requests in Postman Collection format. This feature makes it easy to share API requests with team members, test them in Postman, or bring existing Postman requests into Martini without having to recreate them from scratch.

When To Use This

Use this when you need to:

Prerequisites

Importing Postman Collections into Martini

Bring your existing Postman collections into Martini to test and integrate API requests into your development workflow, services, and automated processes.

Getting Started with Collection Import

Follow these steps to import your Postman collection:

  1. Open the HTTP Client view
  2. Open the import wizard using one of these methods:
    • Click the Import Postman Collection button in the HTTP Client toolbar
    • Use the context menu:
      • Right-click in the Workspace Requests or User Requests area
      • Hover over Import
      • Select Postman Collection
  3. Choose your import source:
    • Upload a local .json collection file, OR
    • Paste a direct link to an online Postman collection
  4. Select destination directory and organize requests:
    • Workspace Requests directory - for project-specific requests
    • User Requests directory - for requests shared across all workspaces
    • Optionally, add new folders to better organize your requests
  5. Click the Import button

Expected result: Your imported HTTP requests appear in the specified directory, organized with the same structure as your original Postman collection.

How Postman Collection Import Works

The import process analyzes your Postman collection and creates Martini HTTP requests based on the collection contents:

Import Process:

  • Collection Analysis: Martini reads the Postman collection JSON structure
  • Compatibility Check: Each request is evaluated for Martini compatibility
  • Request Conversion: Compatible elements are converted to Martini's HTTP request format
  • Default Assignment: Unsupported values fall back to Martini's default settings (e.g., unsupported authentication defaults to None)
  • Folder Creation: Original folder hierarchy is recreated in the destination directory

What Gets Preserved: Collection structure, supported HTTP methods/URLs/headers/bodies, parameters, variables, request names, authentication (if supported), and descriptions (including those for requests, parameters, headers, and variables)

What Gets Lost: Unsupported authentication setups, testing scripts, and Postman-specific features

After Import: Review imported requests and manually configure authentication or testing scripts as needed in Martini.

Troubleshooting Import Issues

Problem Detection Cause Fix
Import fails Error message during import process Corrupt or invalid JSON file Ensure the file is a valid Postman collection JSON
Import process won't proceed Import wizard stops Collection uses Postman v1 format Use Postman Collection v2 format instead

Exporting Martini HTTP Requests as Postman Collections

Convert your Martini HTTP requests into Postman collection format for sharing with teams.

Getting Started with Request Export

Follow these steps to export your HTTP requests:

  1. Open the HTTP Client view
  2. Select the request(s) and/or folder(s) you want to export
  3. Right-click on any selected item
  4. Hover over Export in the context menu
  5. Select Postman Collection
  6. Choose your destination folder and filename for the collection
  7. Save the Postman collection file

Expected result: A .json file is created containing your selected requests in standard Postman collection format, ready for import into Postman or sharing with team members.

How Request Export Works

The export process converts Martini's internal request format to the standard Postman collection schema:

Export Process:

  • Request Enumeration: Martini identifies all selected requests and their configurations
  • Format Conversion: Each request is translated from Martini format to Postman collection structure
  • Structure Organization: Collection hierarchy depends on your selection method
  • Variable Inclusion: Only variables used by exported requests are included
  • Collection Generation: A valid Postman collection JSON file is created

What Gets Preserved: Request names, URLs, HTTP methods, headers, request bodies, parameters, supported authentication settings, and descriptions (including those for requests, parameters, headers, and variables)

What Gets Lost: Authentication configurations not supported in Postman, and test scripts

Collection Structure Behavior:

  • Multiple Individual Requests: Selected requests from different directories are placed at the same level in one collection
  • Folder Selection: Selecting folders preserves the complete nested structure, including subfolders
  • Variable Handling: Only folder variables actually used by the exported requests are included in the collection

The resulting collection is immediately usable in Postman and maintains functional request configurations while adapting the organizational structure based on your selection approach.

Troubleshooting Export Issues

Problem Detection Cause Fix
Missing requests in collection Fewer requests exported than selected Selected requests from both Workspace Requests and User Requests Export workspace and user requests separately - they cannot be combined in a single Postman collection

Helpful Resources