Skip to main content

​
Overview

LiteClient supports importing Postman Collection v2.1 files, including nested folders, requests, and metadata. This allows you to seamlessly migrate your existing API workflows to LiteClient.

​
Supported Format

LiteClient imports:
  • Postman Collection v2.1 JSON files
  • Nested folders and request organization
  • Request metadata (name, description, method, URL)
  • Headers, body, and authentication configurations
LiteClient currently supports Postman Collection v2.1 format. Ensure your collection is in this version before importing.

​
Importing a Postman Collection

1

Open Collections Tab

In the LiteClient sidebar, switch to the Collections tab
2

Click Add Collection

Click the Add Collection button
3

Select Import from Postman

Choose Import from Postman from the options
4

Choose JSON File

Select your Postman Collection v2.1 JSON file from your file system
5

Import Complete

LiteClient automatically imports:
  • All requests with their configurations
  • Folder structure and organization
  • Request metadata and descriptions

​
Exporting from Postman

If you need to export your collection from Postman first:
1

Open Postman

Launch the Postman application
2

Select Collection

Find the collection you want to export in the sidebar
3

Export Collection

  1. Click the three dots (…) next to the collection name
  2. Select Export
  3. Choose Collection v2.1 as the format
  4. Save the JSON file
4

Import to LiteClient

Use the JSON file with LiteClient’s import feature
Make sure to select Collection v2.1 when exporting from Postman. Other versions may not be fully compatible.

​
What Gets Imported

LiteClient imports the following from Postman collections:

Request Configuration

  • HTTP method (GET, POST, etc.)
  • URL and path parameters
  • Headers and values
  • Request body (all types)

Organization

  • Collection name and description
  • Nested folders
  • Request order and hierarchy

Metadata

  • Request names
  • Request descriptions
  • Collection metadata

Authentication

  • API Key configurations
  • Bearer tokens
  • Basic auth settings

​
Exporting from LiteClient

You can also export your LiteClient collections back to Postman format:
1

Open Collections Tab

Navigate to the Collections tab in the sidebar
2

Select Collection

Find the collection you want to export
3

Export Collection

  1. Click the collection menu (three dots)
  2. Select Export
  3. Choose a location to save the JSON file
4

Import to Postman

The exported file can be imported back into Postman if needed

​
Migration Checklist

When migrating from Postman to LiteClient:
  • Export your Postman collection as v2.1 JSON
  • Import the JSON file into LiteClient
  • Verify all requests are present
  • Check folder structure is maintained
  • Recreate any environment variables in LiteClient
  • Test critical requests to ensure they work as expected
  • Configure OAuth flows if using OAuth 2.0 authentication
LiteClient’s variable system works similarly to Postman’s. You can recreate your Postman environments in LiteClient’s Env tab.

​
Differences from Postman

While LiteClient maintains compatibility with Postman collections, there are some differences:
Postman environments need to be recreated manually in LiteClient. Export your Postman environment as JSON, then manually create variables in LiteClient’s Env tab.
LiteClient does not currently support Postman’s pre-request scripts. Use LiteClient’s variable system for dynamic values.
Postman test scripts are not imported. LiteClient focuses on request/response inspection via the native VS Code interface.
LiteClient does not have a collection runner feature. Requests are executed individually.

​
Troubleshooting

  • Verify the file is Postman Collection v2.1 format
  • Check that the JSON file is not corrupted
  • Ensure the file is properly formatted JSON
  • Try re-exporting from Postman if issues persist
  • Check if the requests are nested in folders
  • Expand all folders in the Collections tab
  • Verify the original Postman collection included all requests
  • Re-configure OAuth 2.0 flows in the Auth tab
  • Verify API keys and bearer tokens are set correctly
  • Check that variables used in auth are defined in environments