Skip to main content

Importing from Postman

Move Postman collections and environments into Nidra, then review the few features that need manual migration.

Export from Postman​

Collections​

  1. Open Postman and find the collection.
  2. Open the collection's menu and select Export.
  3. Choose Collection v2.1.
  4. Save the JSON file.

Environments​

  1. Open Postman's environment manager.
  2. Open the environment's menu and select Export.
  3. Save the JSON file.

Keep these exports as a backup until you have verified the migration.

Import into Nidra​

  1. Open Nidra and select Import.
  2. Choose the Postman collection or environment import type.
  3. Select the exported JSON file.
  4. Review the import summary and complete the import.

Import collections one at a time so each result is easy to review.

Compatibility​

Nidra imports the common parts of Postman Collection v2.1 files:

  • Collection folders and requests
  • HTTP methods, URLs, headers, query parameters, and request bodies
  • Basic and bearer authentication
  • Collection and environment variables
  • Pre-request and Tests scripts for manual review

After import, OAuth configuration and scripts that depend on Postman-specific APIs may need adjustment. Postman monitors and Postman-hosted mock servers are not imported.

Verify the import​

  1. Compare the imported folders and request count with the source collection.
  2. Select the intended Nidra environment and review its variable values.
  3. Send representative requests for every authentication and body type in the collection.
  4. Review every imported Pre-request and Tests script.
  5. Save any authentication, script, or assertion changes.

Missing variables​

Confirm that you imported the environment separately, selected it in Nidra, and retained the same variable names used by the requests. Add values that were intentionally excluded from the Postman export, such as secrets.

Authentication failures​

Open the request and collection authentication settings, confirm the imported auth type, and check that its token or credentials resolve from the selected environment. Reconfigure OAuth flows manually when required.

Convert scripts and tests​

Postman scripts use the pm API, while Nidra scripts use the sandboxed nidra API. Replace Postman environment access such as:

pm.environment.set('timestamp', Date.now());

with the Nidra equivalent:

nidra.environment.set('timestamp', String(Date.now()));

Use nidra.request in Pre-request scripts and nidra.response in Tests scripts. See Pre-request & Tests scripting for the complete API and v1 limitations.

Simple Postman response checks can be recreated as Nidra assertions. For example, convert a pm.response.to.have.status(200) test to a status-code assertion configured as equals 200. See Assertions for assertion workflows.

Migrate collection workflows​

Replace Postman Collection Runner workflows with a Conduit:

  1. Create a Conduit.
  2. Add requests in execution order.
  3. Extract response values needed by later steps.
  4. Add assertions for validation.
  5. Run the Conduit and review each step's result.

Learn more in Building Conduits.

Troubleshooting import errors​

  • Export the collection as Collection v2.1 rather than an older schema.
  • Confirm the file contains valid JSON and is readable by your user account.
  • Import the original export rather than a file modified by another tool.
  • If one collection fails, export and import it separately to isolate the unsupported item.

Next steps​