Postman export

In addition to importing API collections from Postman, you can also export mabl API tests back to Postman. The export workflow consists of three steps:

  1. Export a mabl API tests as a Postman collection in JSON file format
  2. Import the file into Postman as a new collection
  3. Run the collection in Postman to verify everything works

Exporting an API test

You can export a mabl API test as a Postman collection from the Test Details page as well as from within the API test editor. Look within the available actions next to the API test flow name to locate the export button. Click on the Export as Postman collection button to download a file in JSON format.


Export an API test flow as Postman collection from the test details page

Managing file uploads

If your test includes file upload steps, the mabl Desktop App displays a list of the corresponding files when you export the test. You can download these files from your mabl workspace to your local machine. When you import the test into Postman, you need to add the file(s) manually to the correct directory.

Importing into Postman

Next, open the Postman application and click on the Import button located around the top left area of the app. This will open up a dialog where you can upload the exported file from mabl.

Once imported, you will see the API collection within the Postman collections. If you click on a request and go its Test tab, you may also see mabl-generated code that accounts for assertions and variables created in mabl without scripting. Please, do not change that script in Postman so that you will be able to import the collection back to mabl without issues.


mabl-generted script after export to Postman.

Running the collection

Next, run the collection in Postman to see that everything works! If the Postman collection run fails, check if all external variables that the API requests rely on are present at the collection and environment level.