Using Watson Assistand/Conversation Service with IBM API Connect (and other API Management solutions) there is a strong need for a swagger specification of the WCS API in file format describing the API calls and its in- and output of the currently provided service.
This file-based specification (e.g. json, yaml) can be used for importing into API Connect for managing and controlling the client use of those APIs. For security reasons the API responses for WCS requests need to be validated against the provided schemas.
As the WCS service does change and enhance over time, every time a new service releases is provided the appropriate swagger specification for the APIs is needed again to continue the validation of the new response payload.
IBM would need to provide such a file-based specification for each new API version which is provided. A documentation is available but not sufficient for this case.