SwaggerHub Feature Requests

For the SaaS SwaggerHub is there is no option to- Add terms-and-conditions SwaggerHub On-Premise has this option https://support.smartbear.com/swaggerhub/docs/enterprise/v1/config/terms-and-conditions.html?sbsearch=login%20page   Since this feature is already available in the “On-prem” version, it is not too much of an ask to incorporate this in the “SaaS” version.    Many organizations are required to inform their users that they are leaving the internal network and going to the external cloud. This feature would be very helpful to inform our customer every time they login along with other critical terms.     ... View more

Hello Smartbear,   Could you please enable a feature of allowing standardization ACROSS organizations? (On premise version) This would solve a lot of stuff in the way we are trying to use this feature and would allow us to organize and categorize our APIs in a more efficient way. Thanks a lot. thanks for voting up 👍👍👍   Kind regards, Adriaan ... View more

Hello I am using SwaggerHub on-premise.   When manipulating APIs, I can use the following: - Fork API file to org/project - Manage Owner and project   For example, I can move an API from organization to another within the wanted project. However, when doing the same, for the same organization but within another project, it keeps the API in the original project and adding it the target project.   It will be cool to really move an API from project to project, within the same organization, and keep only the target project. thanks ... View more

Hello   My company is using SwaggerHub On-Premise and APIGee as API gateway.   We implemented some "Standardization" rules to validate the OpenAPI file syntax within the YAML IDE. Then we run a separated API provided by Google, to validate the OpenAPI file and services logic (here) It would be great to have this validator simply imbedded as an option of the SwaggerHub IDE. By the way, we had cerate a webhook to run it as an integration. Thank you ... View more

Could you please consider proxying any authenticated calls from the Confluence page to the SwaggerHub API back through the domain that you presumably serve the widget content from (https://confluence-plugin.swaggerhub.com)? I'm not sure what constraints exist with the Confluence plugin model, but hopefully this would allow you to manage all sensitive state (ApiKey storage) externally in a location we already trust, and form the appropriate authenticated requests to the SwaggerHub API from there.   As things stand right now, the SwaggerHub API requests are observable using browser dev tools as the Confluence page renders. These requests include the chosen SwaggerHub ApiKey in the authorization header. This is a security concern for us as we have external parties and partners who we grant visibility to areas of our Confluence tenant so they can view documentation which includes api specifications. Once the ApiKey is compromised, the holder has far more than the readonly-access to specific API specifications that we intended.   There are probably other ways to address this, but the proxy approach seemed the most pragmatic to me. We've worked around this issue in the past with other Confluence swagger plugins by only using exported specifications that are attached to the page. However, you are in a good position to allow the convenient referencing of the api specifications in their natural home in SwaggerHub, while keeping the communication paths secure. ... View more

Would be useful to allow just the base url to a SwaggerHub API to be specified in the widget configuration. For example: https://api.swaggerhub.com/apis/acme/products Rather than: https://api.swaggerhub.com/apis/acme/products/1.1.0   When the Confluence page is later browsed (and assuming the url is to SwaggerHub), then the default API version should be automatically resolved. This would allow the current state of the API to be reflected in Confluence without requiring new edits every time a new version is published in SwaggerHub.   An extension to this would be to allow the users to choose from the different published versions when browsing the page. This should be an opt-in feature on the widget configuration. ... View more

The User Management and Registry AIs are very useful - but I'm missing any way of viewing or manipulating team membership.   For a specific use case - my organisation is shared among a number of teams that don't have much to do with each other. I want to be able to do things like report on all users in a team, the type of license currently assigned to them, and when they last logged in. The user management API allows me to do most of that, but I can only get the results for the entire organisation - I can't limit it to just the users I'm responsible for.   So, the two main things that would be useful: The existing operation for listing organisation members needs a "filter by team" parameter. Some new operations are needed for listing (and optionally, modifying) the members of a team. It would also be nice if "last active time" was one of the sort options for the API. ... View more

Hi! I`ve found something interesting. I cant make Markdown list option in the properties description when i`m using only Cyrillic symbols. To do this i have to take first symbol from Latin alphabet. For example, here is the description with first Latin char:     As we see, it`s Ok. But, if i insert Cyrillic char as a first symbol, the list is being destroyed:   ... View more

Highly nested objects in schema view are very hard to read.  Is there a better way to do this? Note this is the only way to make the Delivery object and the Address object "nullable". ... View more

It seems like the diffing tools used for APIs are not available for domains. Diffing domains would make things much easier for our development team. Thanks! ... View more

Currently, the developers have a pipeline that acts like a user and uploads generated templates to SwaggerHub. It would be nice if this was an official API route so we are not burdened by UI changes that might break our process. Part of the purpose is so we can validate in our staging SwaggerHub that our end to end flows are working properly. We also trigger a maintenance restart as part of this process for the templates to appear in the UI. Please let me know if you need more detail. ... View more

Each organization should have a wiki page - or at least a stored/clickable URL to enterprise wiki/confluence - so that viewers/developers can get to general doc page of info about the org, dev policies, services standards, etc, whatever. The link would be visible (if set) on the main org API listing page, under the org name. Also in the API editing page in the pulldown section (which lists owner/created by/created date) ... View more

Please extend the search functionality so searches on API paths can be performed. Ideally with autocompletion so it will be easier to explore the existing API paths of an organisation. ... View more

Owners should have a centralized overview of comments that have not been resolved. ... View more

When creating a new version of an API, all comments of the previous version are "lost": they stay in the previous version and become much less visible to the collaborator. ... View more

With multiple users invited that means that the admin/owner needs to log in every day to check if someone has accepted the invitation and the appropriate team should be updated. Especially tricky with users/consumers from other companies. ... View more

Sort order needs to be remembered (ideally it would be remembered across sessions - I almost always want the list sorted by name, not by changed date). - Change the sort order - Click on one of the API's - Click the <- arrow to go back to the list. - Click on the API / Domains on the left menu, suddenly it has reset back to sort by change date. It would be nice if the column to the right of Summary info/Tags/Servers on an API was collapsible (so you could see the info in the list and the full API - you don't always need the summary/tag/server details). This would let you still click on the API methods to scroll to them but not take up horizontal space. It would be nice if there was a way to see where (which API calls) a given model/schema was being used in. Your plan pricing is weird. Only 20 API's for a plan that can have up to 3 designers? We're a tiny team and we're already at 17 of them just after loading the API's provided to us from one of our third-party vendors. We won't even have enough API's if we start importing our own. Our main use case for the site is being able to easily share/view the Swagger docs provided to us vs. us designing our own (which, even if we wanted to, we couldn't use because of the really low API limit). It would be more useful if the "Search within MyHub" could search within the API's as well. We run into the scenario where we are looking for something within a microservice and can't remember which one of the 17 different Swagger docs we have has a particular API call. ex. we might know it's called "validate" (something) but can't remember how the vendor organized it. Right now we have to click into each API and look for it / use the search from there. ... View more

It would be very useful Models could be given tags so that the documentation could group them the same way that the endpoints are grouped. Then in model generation, instead of all of the models in the model folder, they could be split up into sub folders in the model folder.    Not sure if this is swaggerhub Idea, or more for the swagger-generation/swagger-editor repositories, but this is something I would like swaggerhub to do. ... View more

Currently we can push to a branch in github the swagger file only. It would be great if we could also have the ability to create a branch and submit a PR at the same time. This would allow my developers to review and feedback. Having the PR status with the swaggerhub UI would be good too ... View more