We have tried automated code generation several times, and I think maybe some people are still using it somewhere, but it is not something that we do as a consolidated practice. At some point, we were missing some tagging of the APIs, and we could not do that. We asked the provider, but I do not believe they added that kind of support. However, we somehow gave up a bit because we are now in the process of moving to different platforms ourselves, so most likely we are not going to invest in improving this integration with SwaggerHub or how we are using it. We will just keep it going for the platform we are leaving, and then because our focus is in a different place, we are not looking to change or do other things. I am not using SwaggerHub's OpenAI management feature. We are not looking much at what they added new. We got some notification that they added things, but we have so many other things to do.
In SwaggerHub, I appreciate that it is a powerful platform for API design and collaboration, but currently, the access control is somewhat limited. I would love to see enhanced permissions allowing a user to comment without edit access or granting edit access to specific sections of the API specification. Better integration with CI/CD pipelines would also be beneficial, making the integrations more native and streamlined, especially for managing API specifications across different environments while avoiding manual duplications or workarounds.
Director/Enterprise Solutions Architect, Technology Advisor at Kyndryl
Real User
Top 5
Feb 5, 2025
Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account. The scalability also needs enhancement, as it becomes flaky under increased load. Additionally, the versioning management could be improved to be on par with source code management tools.
I noticed that the editor on SwaggerHub, like Gabbiti, is graphical in nature. With this mind map interface, one can easily define endpoints and paths. The solution is lacking behind because it not only define the contract. It define and use one-time policies.
Compared with tools like Postman and SoapUI, it offers similar functionality but is a licensed platform. It provides features for building and managing APIs, including advanced capabilities like designing endpoints and generating documentation. Unlike Postman and SoapUI, which primarily focus on testing APIs, SwaggerHub allows for comprehensive API design and collaboration. It enables users to create, organize, and share API definitions efficiently. SwaggerHub essentially empowers developers to design, document, and maintain APIs seamlessly.
We want some regulatory control to understand who is reading our documentation in the space where we are active. It would be interesting to see who is looking for our API documentation, so that would be one way to understand the users. If it supports public API documentation, it's public. You never know who is likely to use it. There are other smaller things like tagging APIs and various other details. The workflow for editing to offer OpenAPI is not as rich as we would like, so we did the editing with other tools. Additionally, you cannot include additional pages explaining certain workflows you can do with the API. These additional content pages would enhance the OpenAPI specification for the API. So these things are not significant, but they can make a difference when you don't have them.
The review process should be improved. There seem to be some gaps, at least for us, for the editing part because we would like to have a full request review mechanism. They support some comments, but it is really hard to manage those comments. We would like to use the full request. Therefore, we are now looking to integrate with repositories. It has integration with Bitbucket and GitHub, but we have some internal constraints, and we need to move some of the repositories to GitHub. Our source code is on-premise in Bitbucket, and it was a bit of a problem for us to integrate. Now we are transitioning our repositories to GitHub, and hopefully, we can enable the integration. This will probably solve the problem with the review and approval. Its customization should also be improved. There are limitations around the support for the developer portal. There should be more customization options for the website that you can use as a developer portal. Currently, it has only Swagger UI with minimal customization. You cannot actually add additional pages and documentation for explaining concepts and general things. That's why we have started to look around to see what other tools are doing. They should also allow tagging on the API. We would like to add some tagging on the API to reflect certain things. Currently, any metadata that you would like to have has to be a part of the spec. You cannot do anything else. It should also have support for Open API 3.1, which was released at the beginning of the year. It would be great to be able to switch to that.
SwaggerHub is an integrated API Development platform, built for teams, that brings the core capabilities of the Swagger framework to design, build, document and deploy APIs. SwaggerHub enables development teams to collaborate and coordinate the entire lifecycle of an API with the flexibility to integrate with the toolset of your choice.
We have tried automated code generation several times, and I think maybe some people are still using it somewhere, but it is not something that we do as a consolidated practice. At some point, we were missing some tagging of the APIs, and we could not do that. We asked the provider, but I do not believe they added that kind of support. However, we somehow gave up a bit because we are now in the process of moving to different platforms ourselves, so most likely we are not going to invest in improving this integration with SwaggerHub or how we are using it. We will just keep it going for the platform we are leaving, and then because our focus is in a different place, we are not looking to change or do other things. I am not using SwaggerHub's OpenAI management feature. We are not looking much at what they added new. We got some notification that they added things, but we have so many other things to do.
In SwaggerHub, I appreciate that it is a powerful platform for API design and collaboration, but currently, the access control is somewhat limited. I would love to see enhanced permissions allowing a user to comment without edit access or granting edit access to specific sections of the API specification. Better integration with CI/CD pipelines would also be beneficial, making the integrations more native and streamlined, especially for managing API specifications across different environments while avoiding manual duplications or workarounds.
Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account. The scalability also needs enhancement, as it becomes flaky under increased load. Additionally, the versioning management could be improved to be on par with source code management tools.
I noticed that the editor on SwaggerHub, like Gabbiti, is graphical in nature. With this mind map interface, one can easily define endpoints and paths. The solution is lacking behind because it not only define the contract. It define and use one-time policies.
Compared with tools like Postman and SoapUI, it offers similar functionality but is a licensed platform. It provides features for building and managing APIs, including advanced capabilities like designing endpoints and generating documentation. Unlike Postman and SoapUI, which primarily focus on testing APIs, SwaggerHub allows for comprehensive API design and collaboration. It enables users to create, organize, and share API definitions efficiently. SwaggerHub essentially empowers developers to design, document, and maintain APIs seamlessly.
We have to use additional tools to test APIs.
We want some regulatory control to understand who is reading our documentation in the space where we are active. It would be interesting to see who is looking for our API documentation, so that would be one way to understand the users. If it supports public API documentation, it's public. You never know who is likely to use it. There are other smaller things like tagging APIs and various other details. The workflow for editing to offer OpenAPI is not as rich as we would like, so we did the editing with other tools. Additionally, you cannot include additional pages explaining certain workflows you can do with the API. These additional content pages would enhance the OpenAPI specification for the API. So these things are not significant, but they can make a difference when you don't have them.
The solution could be more intuitive compared to Postman. They should improve this particular area.
SwaggerHub could be improved with better integration for tools.
The review process should be improved. There seem to be some gaps, at least for us, for the editing part because we would like to have a full request review mechanism. They support some comments, but it is really hard to manage those comments. We would like to use the full request. Therefore, we are now looking to integrate with repositories. It has integration with Bitbucket and GitHub, but we have some internal constraints, and we need to move some of the repositories to GitHub. Our source code is on-premise in Bitbucket, and it was a bit of a problem for us to integrate. Now we are transitioning our repositories to GitHub, and hopefully, we can enable the integration. This will probably solve the problem with the review and approval. Its customization should also be improved. There are limitations around the support for the developer portal. There should be more customization options for the website that you can use as a developer portal. Currently, it has only Swagger UI with minimal customization. You cannot actually add additional pages and documentation for explaining concepts and general things. That's why we have started to look around to see what other tools are doing. They should also allow tagging on the API. We would like to add some tagging on the API to reflect certain things. Currently, any metadata that you would like to have has to be a part of the spec. You cannot do anything else. It should also have support for Open API 3.1, which was released at the beginning of the year. It would be great to be able to switch to that.
More integration and usability with the cloud microservices would be nice. Azure and GCP — there are multiple platforms we could talk about.