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.
API (application programming interface) management is the process of managing different API functions, such as designing, releasing, documenting, analyzing, and monitoring APIs in a safe environment.
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.