Importing openapi3 with path variable

[navigation-meteorolo (Michael)]

The current way that postman imports openapi into :variable notation means that a path variable cannot be set at an environment level.

So for example, this valid spec that requires an orgId in the path for every request
https://api.m3ter.com/spec

requires adding that into the params for every single request in the collection, or in the case of having a different value for an environment, adding the variable name to the path params for orgId for each request

Is there a way to bulk add this value?

It seems odd that you can’t have path params in environment variables, it is not unusual to have this kind of api endpoint be environment specific.

[daniel-abernathy-rz (Daniel Abernathy)]

Trying out Postman today and running into this same issue. Path parameters are a great feature, but we should be able to map the values to variables on import. Right now I have hundreds of requests that each need to have multiple path parameters manually assigned to map to an environment variable.