Import Postman Collection v2 exports into editable Multimeter projects.
Markdown (no JavaScript)
# Postman Import Postman Collection v2 exports into editable Multimeter projects. ## Run directly See [Spec editor](./spec-editor.md) for the {{btn:list-tree}} request picker and {{btn:save-as}}. In VS Code, right-click a Postman collection JSON file and choose **Open as MMT**, or use **Open With...** → **Multimeter Spec Editor**. The collection stays on the left. Click {{btn:list-tree}}, pick a **request** or a **saved example** ({{btn:lightbulb}} child row), then {{btn:send:Send}}. There is no **All** row for Postman collections in the spec editor — run requests one at a time, or use **Convert to MMT** below for a full project. Hover a row for **Save as MMT**. ## Convert to MMT 1. Export or save your Postman collection as JSON 2. Right-click the collection file in the VS Code Explorer 3. Choose **Convert to MMT...** 4. Select the generated files, pick a destination folder, and choose a collision policy Multimeter turns collection requests into `type: api` files and optional tests and suites you can run in the UI or with Testlight. ## What gets generated - **API files** — protocol, method, URL, headers, body, inputs, and examples when available - **Tests** — one test per request that imports and calls the generated API - **Suites** — Postman folders become suites that run folder tests and child-folder suites in sequence - **Large collections** (5+ APIs) — also generate `multimeter.mmt` with `+/` imports - **Environment file** — collection variables and referenced credentials become editable variables ## Postman-specific mapping - Dynamic variables (`{{$guid}}`, `{{$randomEmail}}`, `{{$randomInt}}`, names, network values, company data, and Lorem text) → matching Multimeter `r:` tokens; JSON bodies parse into structured YAML with native `r:` fields (including unquoted `{{$timestamp}}` values) - Common `pm.variables.replaceIn('{{$timestamp}}{{$randomInt}}')` pre-request scripts → translated `setenv` steps - Collection and folder auth is inherited by requests; request-level `noauth` overrides it - Bearer, basic, API key, and OAuth2 client-credentials auth map directly - Interactive OAuth2 becomes a bearer `access_token` environment variable - GraphQL bodies become `protocol: graphql`; file bodies with a source path become binary requests - URL path variables become API inputs, and disabled headers/query fields remain omitted - `urlencoded` bodies map directly; multipart form-data with files produces a manual-review warning - Saved response examples with `originalRequest` → auto-generated inputs, header placeholders, and example overrides - Common status assertions, response variable assignments, UUIDs, timestamps, and request-header assignments are translated - Unsupported Postman scripts are preserved as commented `js` steps with review warnings, so missing `pm.*` globals cannot break a run OAuth1, multipart file uploads without source paths, and complex Postman sandbox APIs still need manual work after import. Conversion warnings identify affected requests. ## Tips after import - Map your base URL to an environment variable (for example `api_url`) and reference it with `<<e:api_url>>` - Review generated inputs and headers — tweak names to match your project - Use the API editor to refine bodies and add `setenv` for downstream tests Example output: [Postman convert example](../../examples/intermediate/25_convert_to_mmt/postman/README.md) Full sandbox Postman collection: [professional Postman convert](../../examples/professional/04_convert_to_mmt/postman/README.md) ## See also - [OpenAPI spec](./openapi.md) · [HTTP file](./http-file.md) · [Bruno](./bruno.md) · [Environment](../files/env/index.md)
For AI agents · llms.txt · Home