Generate postman collection from asp.net core

[arisliang]

We have an asp.net core project and using postman. We like it both. However, in order to test it in postman, we have to manually create the postman requests to call the web API.

Is there a way to scan through the web API, and create / update them in postman automatically?

[arisliang]

PS, we're using a paid version of postman, if that helps.

[abhijitkane]

@arisliang Not yet. Would love to know more about your workflow, though. Is any of the code publicly available? Feel free to reach out on help@getpostman.com as well.

[STeeL835]

We get around this by using NSwag (or Swashbuckle, but we need to generate C#/TS clients too) to generate OpenAPI spec, that we can later use to generate the collection.

The problem here is that Postman is built around editing the api/collections in the app only, has forks, teams, apis, etc, when our reality is generation of spec/collection using our methods (NSwag in our case + combination of scripts to generate a collection with everything we need), programmatically, which is a much more flexible method to us.

These 2 worlds don't come together very good, because Postman

• Doesn't have a way to automatically import/export collections/openapi specs (whether it's synching with files in a folder or a CLI for scripting)
• Doesn't have a way to re-import collections without deleting them first
  • and "Skip importing files every time" popup is promoting features useless for us, because we can't use forks in our case and can't "merge" such generated collections if we had a team. Either way, forks in postman don't seem to be very mature for merges, because you can't really control what you want to save, or see change history like in git.