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 Oct 12, 2026

Allow custom vanity endpoints for Nano Gateway APIs

We are migrating our API gateways from Kong to the IBM API Connect Nano Gateway and have started a proof of concept by deploying our first API.

By default, the Nano Gateway generates a vanity endpoint in this format:

https://<api>-<product>-<catalog>.<gatewayDomain>/<basePath>/<version>

We need to preserve our existing API URLs so the migration is transparent to consumers. Changing the hostname or path would require consumer changes and could disrupt existing integrations.

Could Nano Gateway support configuring a custom hostname and path for an API, independent of the API, product, catalog, base path, and version naming? Ideally, this could be set during API or product configuration, while retaining validation to prevent conflicting routes.

This would let customers migrate to Nano Gateway without changing the endpoints already used by their consumers.

Idea priority Urgent