Ask a Question

Persistence of Integrations at the API (not version) and organizational levels

Persistence of Integrations at the API (not version) and organizational levels

We have several APIs and in order to integrate these with Azure and BitBucket, I have to provide the integration details on every API version; which gets daunting.  I'd like to be able to set this at the API container level or organization level so I don't have to reset them again.

New Member

Yes, please add this feature. We're planning to use the SwaggerHub to keep track of all of our internal APIs, probably close to 50. Imagine having to fill out all the integration plugin forms by hand for multiple integrations per api per version.


Maybe then also introduce some kind of variable substitution in the plugin configurations. The `branch` name for the SCM plugins could then be configured as `swaggerhub-${apiVersion}` for instance?


As an intermediate option perhaps it could be an idea to offer the user the option to copy integrations from another version? 

SmartBear Alumni (Retired)
Status changed to: New Idea
New Contributor

I also would find this feature useful - particularily the templating - as I want to do this: sync each API with a folder in the same repo in Git Azure DevOps with the path /APIs/<<API_NAME>>/<<Version>>, presently I will need to configure each one of these separately. Thanks.

Status changed to: Selected for Development

This has been implemented for Source Control integrations (GitHub, BitBucket, Azure DevOps, GitLab)

Status changed to: Implemented
Welcome to the SwaggerHub Feature Requests board!

Here you can review already submitted feature requests and vote up the ones you like! If you can't find the feature you want - go ahead and suggest your own idea. Ideas with the highest rating can be implemented in the product.

Check out the Create a Feature Request guide for more information.
New Here?
Welcome to the Community
Sign Up Here