You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Feature Request]
It would be hugely beneficial to be able to export an Insomnia workspace into the OpenApi (open-sourced Swagger) spec. There is currently a pretty big hurdle to taking an Insomnia workspace and putting it on a API documentation website, as most of the bigger ones out there take an OpenApi spec to automatically generate documentation.
This would also allow a more interoperable ecosystem, as I could send my insomnia workspaces to other teams who are not using Insomnia, allowing them to use their tool of choice to test our APIs. This is the key sticking point when it comes to getting approval for purchasing the Teams package as a company - as we don't want to promote a tool that will lock us into a specific ecosystem.
The text was updated successfully, but these errors were encountered:
👋 Thanks for opening your first issue! If you're reporting a 🐞 bug, please make sure
you include steps to reproduce it. If you're requesting a feature 🎁, please provide real
use cases that would benefit. 👪
To help make this a smooth process, please be sure you have first read the contributing guidelines.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
[Feature Request]
It would be hugely beneficial to be able to export an Insomnia workspace into the OpenApi (open-sourced Swagger) spec. There is currently a pretty big hurdle to taking an Insomnia workspace and putting it on a API documentation website, as most of the bigger ones out there take an OpenApi spec to automatically generate documentation.
Slate can convert from OpenApi
Apiary supports their in-house as well as OpenApi
Azure can import from OpenApi
Apigee can create an api-proxy from OpenApi spec
This would also allow a more interoperable ecosystem, as I could send my insomnia workspaces to other teams who are not using Insomnia, allowing them to use their tool of choice to test our APIs. This is the key sticking point when it comes to getting approval for purchasing the Teams package as a company - as we don't want to promote a tool that will lock us into a specific ecosystem.
The text was updated successfully, but these errors were encountered: