2
votes

I've set up a pretty extensive set of calls in collections using postman. I use dynamic variables (e.g. {{USERNAME}}) in the URL, headers, and body of these calls that are dynamically replaced by variables from my selected postman environment. I'd like to import this collection (along with environments) to PAW and have the dynamic postman variables be switched to dynamic PAW variables.

I've looked at How do I import from Postman and ensure all of my environment variables will get resolved? which is this exact same question, but the answer (to use the Postman Importer - https://luckymarmot.com/paw/extensions/PostmanImporter) doesn't seem to work completely.

I've tried the latest version of the importer (v2.0.0) and while it appears to convert the dynamic variables I define in the headers of my postman calls, it does not replace those in the URL or request body. After importing to PAW I still have, for example, {{USERNAME}} in my request body.

Any tips would be appreciated.

1

1 Answers

1
votes

We're currently working on a large project that will enable Paw to import many API formats in a lot nicer way (including Postman), we should have something ready by next week, and it will solve the problem you're having for environment variable {{EXAMPLE}} in the URL and the body.

Though, I've checked and it appears that the previous version of the Postman Importer had this environment variable import right. So maybe it's worth giving it a try if you need that today: https://github.com/luckymarmot/Paw-PostmanImporter/releases/tag/v1.2.0

All you have to do, is checkout the repo, checkout the tag v1.2.0 and run npm install and cake install. It should install itself in the Paw extension directory and replace the existing version of the importer.