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 Jun 24, 2020

Better documentation for CLI, REST API and more

API Connect has a lot of hidden good features not comprehensively documented. This can leads to wrong usage, more time for troubleshooting and support, which could be actually be saved for more productive feature development work.

For example, the apic CLI documentation in KC often describe a 'create' operation with no detailed explanation or sample and often different than the real command line live help, like missing argument SOME_FILE. There is no description of schema describing the expected FILE. This makes the command hardly usable.

Another example for REST API is the POST /token API, which describes in the schema 5 different grant types to return a token. But there is no documentation about when and how to use which grant type. Also, no documentation about related other properties like assertion, realm, code.

The REST API documentation of APIC should be the best API specification showcase for itself, shouldn't it?

Idea priority Urgent
RFE ID 143460
RFE Product IBM API Connect