We have created an API from scratch in the wM.io APi Gateway. We have added a custom gateway endpoint to the API and published it to the API portal.
However, when a client downloads the API specifications from the portal, it only lists the default gateway endpoint in the server url section. Downloading the API specification from API Gateway also has the same issue.
Is there a way to include the custom gateway endpoints within the API specifications? There is no point for us to add them into the API when the clients cannot import those directly from the spec.