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.


Add a new idea Subscribe
Status Submitted
Workspace API Connect
Created by Guest
Created on Sep 1, 2026

RELATED IDEAS

OpenAPI 3 multiple-server gateway and vanity endpoint support

Allow multiple entries in the OpenAPI 3 servers array to produce distinct, invokable vanity endpoints instead of using only the first entry to determine the gateway route.

 

Background: We have ~50 internal environments.  Different teams use different environments for different things.  APIs in the catalog may typically be connected to ~10 different environments.  We have a firm requirement from our leadership to use the hostname to determine the destination environment, not a parameter.  Catalog vanity endpoints are not a good fit, since it would be confusing to users if only 10/50 of the available hostnames worked for a given API.

It has been a challenge for us to implement API vanity urls because the first server becomes part of the API path.  It would be great if there were an option to (1) not have the hostname as part of the API path, or (2) all hostnames in the API vanity urls would work.

Here's a simple example:

Servers: dev.api.example.com & test.api.example.com.

Currently, the API URL would be https://dev.api.example.com/pOrg/catalog/dev.api.healthpartners.com/apiPath/... and https://test.api.example.com/pOrg/catalog/dev.api.healthpartners.com/apiPath/...

It would be nice if the API URLs could be either:

  1.  https://dev.api.example.com/pOrg/catalog/apiPath/...
    https://test.api.example.com/pOrg/catalog/apiPath/...
    or
  2. https://dev.api.example.com/pOrg/catalog/dev.api.healthpartners.com/apiPath/...
    https://test.api.example.com/pOrg/catalog/test.api.healthpartners.com/apiPath/...

Please see the linked support case for more detail, or reach out to me.

 

Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.