The REST API docs should publish a Postman collection/OpenAPI specification to aid in developer understanding and help facilitate application integration.
I also need to create a bridge between Kanabanize and Aha! using IBM APP Connect product and such APIs are needed to do this.
IBM APP Connect offers a simple way to just import such definitons collected in a yaml file and simply maps the actions for a mirroring bettwen the two tools.
Please, prioritize this requirement to have such OpenAPIs available ASAP.
Agreed 100%. Without a standardized spec, implementing Aha's API is a huge undertaking because of the amount of options available, and the only way to browse it is through Aha's proprietary documentation.
As an example use case: I would like to create a connector for our Aha instance in Microsoft's Power Automate, which is a self-service automation platform similar to Zapier. A Postman collection or OpenAPI spec enables me to quickly create and use this connector. Without it, I have to manually define every single input that I want to be able to use, including return codes, response schema, etc.
I also need to create a bridge between Kanabanize and Aha! using IBM APP Connect product and such APIs are needed to do this.
IBM APP Connect offers a simple way to just import such definitons collected in a yaml file and simply maps the actions for a mirroring bettwen the two tools.
Please, prioritize this requirement to have such OpenAPIs available ASAP.
Sad to see this doesn't already exist. It's so much easier to go from Postman to Python or Powershell than it is from swagger.
Agreed 100%. Without a standardized spec, implementing Aha's API is a huge undertaking because of the amount of options available, and the only way to browse it is through Aha's proprietary documentation.
As an example use case: I would like to create a connector for our Aha instance in Microsoft's Power Automate, which is a self-service automation platform similar to Zapier. A Postman collection or OpenAPI spec enables me to quickly create and use this connector. Without it, I have to manually define every single input that I want to be able to use, including return codes, response schema, etc.