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.

Status Future consideration
Workspace API Connect
Created by Guest
Created on Sep 20, 2022

Validate on publishing for missing general properties when catalog properties are used

Hi everybody,

Currently the API Manager does not recognize if an API provider is trying to deploy an API defining a property on catalog level (e.g., and misses to define it in the global properties (

Example YAML:




value: ''

description: The URL of the target service

encoded: false





target-url-asia: ''

target-url-europe: ''

In this example when calling the API in Dev catalog, the target-url-europe will not be available to be used in the assembly. This is very confusing to the users and they run into this on a regular basis.

I think the API Manager should recognize this on deployment and return an error message stating the missing global property and its name.

We are deploying using the API Product API, so I think this would be a good place to implement the validation for this.

Idea priority Medium