Import & Export

Import Postman

Ironcall imports Postman Collection v2.1 format. Go to File > Import and select your .json export file. Requests, folders, headers, query parameters, bodies, and authentication are imported. Auth configurations are mapped to their Ironcall equivalents where possible.

To export from Postman: open the collection, click the three-dot menu, and select Export. Choose Collection v2.1.

Import Insomnia

Ironcall imports Insomnia v4 and v5 export files. Go to File > Import, select your Insomnia export, and choose Insomnia as the format. Requests, folders, headers, parameters, bodies, and authentication are imported.

To export from Insomnia: go to Application > Preferences > Data, then Export Data.

What does not carry over

Pre-request and test scripts from Postman and Insomnia are not imported. Ironcall uses a different scripting model (see Scripts), so these are skipped rather than translated incorrectly. Review any auth or script-driven behaviour after importing.

Environment files are imported separately from collections. Import the collection first, then import its environment export.

Import modes

When the import would create items that already exist, you choose how to resolve it:

• Copy: keep both the existing items and the imported ones.
• Replace: remove the existing items, then import.

Export YAML

Right-click a collection in the sidebar and select Export. The collection is written to a directory of YAML files that mirrors the collection hierarchy, with one file per request and a _folder.yaml per folder for folder metadata, scripts, and variables.

Secret variable values are redacted on export: the key is preserved and the value is replaced with REDACTED.

The YAML format is Ironcall's native format. It is human-readable and diff-friendly, making it suitable for version control alongside your codebase. Ironcall reads back both YAML and JSON, and always writes YAML.