Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Workspace API Connect
Created by Guest
Created on Dec 14, 2018
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit APICONN-I-385 Remove x-ibm-attributes in OpenAPI Spec file that can be downloaded in dev portal.

Pubic OpenAPI - Spec in Dev Portal should not contain any x-ibm- attributes Merged

A Rest-API is published in a developer portal. We use properties like target-url in invoke policy.
When a user downloads the OpenAPI spec file in dev portal, the file still contains x-ibm- ... attributes, like x-ibm-configuration (see attachment).

This information is not necessary for using the public gateway endpoint. It also violates the principle of segregating interface and implementation. There should be no implementation-specific information in an api contract.

What is even worse: the property target-url, which points to an internal backend system is leaked into the public. We consider this a security issue (we will provide APIs to the internet community nor do we want to let everbody know, were using IBM).

Please remove any ibm-specific attributes from the OpenAPI spec file that can be downloaded in the dev portal.

Idea priority High
RFE ID 128330
RFE Product IBM API Connect