Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Workspace API Connect
Created by Guest
Created on Sep 1, 2026

Support Multiple Server Hostnames For Swagger v2 APIs

Provide a supported API Connect mechanism for associating multiple environment-specific endpoints with an OpenAPI 2 API, even though the OpenAPI 2 specification provides only a single host field.

 

Our organization works a lot with Swagger v2 and OpenAPI v3 APIs.  We have a requirement to use custom hostnames with API vanity URLs.  We need to display the different endpoints to users on the portal, so we're left with the unenviable options of:

  1. Create 1 API definition for each Swagger v2 custom hostname.  This creates a significant amount of extra work and was not recommended by IBM Support.
  2. Convert all Swagger v2 API definitions to OpenAPI v3.  This is a challenge because our upstream partners may still only present Swagger v2 API definitions to us, so we'll be continually converting until they decide to upgrade.

The API Manager UI and Developer Portal UI can support multiple hostnames for OpenAPI v3.  We would like similar options exposed for Swagger v2, even though this is not part of the standard.  It would be OK with us if users downloaded the Swagger v2 definitions and it only included the first hostname.

Idea priority Low