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 Submitted
Workspace API Connect
Created by Guest
Created on Apr 29, 2024

Change the visibility of public product APIs for anonymous users in the DevPortal

As you know, there are 3 ways to configure the visibility of products when they are published in the catalog (Public/Authenticated/Custom). If products are published as Authenticated, customers' browsing is limited, forcing them to create a DevPortal account to view them.

It would help to open up some level of visibility for products, restricting access to the API page. In this way, customers will be able to see the products, their descriptions, the APIs contained and the plans without needing an account. To access the API documentation, their operations and endpoints they must create an account.

There are modules in Drupal that as administrators allow us to restrict access to certain content, but it does not work as we expected. We suspect that there is some APIC rule that takes precedence over the module configuration.

What we are looking for is to make the restriction of authenticated visibility more flexible, ensuring that clients have access to the product catalog, the details of each product, but not to the APIs that the product contains. This is to prevent attacks by exposing API consumption endpoints.
Idea priority Urgent