I arrived here from Google searches as well. It’s a bit mind boggling that this is not available. I was trying to switch over to use Postman from other solutions, but if I have to recreate every time it’s very frustrating. I guess their use case is “use our too for everything” and if you don’t fall into that case too bad 
Disappointing because I was excited to see how well it handled the original import.
1 Like
In the same boat. The answer is it doesn’t work, they built something different instead. I was also shocked it was not possible and still is not!
1 Like
Welcome to the Postman Community! 
As this is an older thread going back to 2019 
, would you mind providing some information and context to the issue you’re currently facing in the latest version, please? 
I was lamenting that syncing OpenAPI spec to a collection is not possible and the fact that Postman saw this and reacted and built something that was very different than what users were looking for and kinda called it a day.
I’ve run into multiple show-stopper bugs (in 2 days of usage) while using the latest version of this and I’ll be honest that I’m not interested in spending my time documenting them and working with your teams to get them sorted out. A quick example, try having an OpenAPI 3.1 spec that you import that uses the name “record” for a variable on an endpoint and see what happens 
– for me it built incorrect and unusable endpoints that I had to fix by hand and the issue was very obviously around parsing the spec.
1 Like
Appreciate you responding @satellite-astronaut2
Two way sync is available for v3.0 but it’s currently not supported for v3.1 but this is coming.
We’ve also tried to replicate the issue that you mentioned but that seems to be working as expected:
We’d love to explore this and the other issue that you found, if you could share some more information.
1 Like