Skip to main content

Importing from Postman

Switching from Postman to Nidra? Import your existing Postman collections seamlessly.

What You'll Learn​

  • How to export collections from Postman
  • Import Postman collections into Nidra
  • What gets imported and what doesn't
  • Migrating environments and variables

Exporting from Postman​

Exporting Collections​

  1. Open Postman
  2. Right-click the collection to export
  3. Select "Export"
  4. Choose "Collection v2.1" (recommended)
  5. Save the JSON file

Exporting Environments​

  1. Click the environment gear icon in Postman
  2. Click the download icon next to the environment
  3. Save the JSON file

Importing into Nidra​

Import Collection​

  1. Open Nidra
  2. Click "Import"
  3. Select "Postman Collection"
  4. Choose your exported collection file
  5. Configure import options
  6. Click "Import"

Import Environment​

  1. Click "Environments"
  2. Click "Import"
  3. Select "Postman Environment"
  4. Choose your exported environment file
  5. Click "Import"

What Gets Imported​

Nidra imports:

Collections:

  • Folders and organization
  • Requests (method, URL, headers, body)
  • Pre-request scripts (with limitations)
  • Tests (converted to assertions where possible)
  • Authentication settings
  • Variables

Environments:

  • All variables
  • Variable types
  • Initial and current values

Compatibility Notes​

Fully Supported​

  • All HTTP methods
  • Headers and query parameters
  • Request bodies (JSON, form-data, etc.)
  • Basic authentication
  • Bearer token authentication
  • Environment variables

Partial Support​

  • Scripts (converted to equivalent Nidra features)
  • Tests (converted to assertions where syntax is compatible)
  • OAuth flows (may require reconfiguration)

Not Supported​

  • Postman monitors
  • Postman mock servers
  • Some advanced scripting features

Post-Import Steps​

After importing:

  1. Review the collection structure: Verify folders and requests
  2. Test key requests: Ensure they work as expected
  3. Check variables: Verify environment variables are correct
  4. Update scripts: Convert any Postman scripts to Nidra equivalents
  5. Migrate tests: Convert test assertions to Nidra format

Converting Postman Tests to Assertions​

Postman tests are JavaScript snippets. Nidra uses a declarative assertion format.

Example: Postman test

pm.test("Status code is 200", function () {
    pm.response.to.have.status(200);
});

Equivalent: Nidra assertion

Status Code equals 200

Learn more about assertions →

Converting Pre-Request Scripts​

Postman pre-request scripts can set variables. In Nidra:

Postman:

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

Nidra:

Use variable extraction or conduit variable steps.

Migrating Workflows​

If you use Postman's Collection Runner:

  1. Create a Conduit in Nidra
  2. Add the requests in order
  3. Set up variable extraction
  4. Add assertions for validation

Learn about Conduits →

Troubleshooting​

Import Errors​

If import fails:

  • Ensure you exported as Collection v2.1 format
  • Verify the JSON file is valid
  • Check file permissions

Missing Variables​

Authentication Issues​

Best Practices​

  • Import one collection at a time: Easier to verify and debug
  • Test thoroughly: Verify all critical requests work
  • Update documentation: Note any changes from Postman workflow
  • Train your team: Ensure everyone understands Nidra equivalents
  • Keep a backup: Maintain Postman exports until migration is complete

Next Steps​