Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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 Functionality already exists
Workspace SevOne
Created by Guest
Created on Aug 27, 2024

Add end user facing documentation in v3 API IBM developer pages

With SOAP being deprecated already from the ongoing supported API access and the desire to retire API v2, we need to ensure end users/customers are able to efficiently use the v3 API and complete documentation is the key to this succeeding.  Without the description of what the API call exists for as the intended use from the system perspective, it can be confusing as to what calls do or are intended to be utilized for in implementation.  This addition will support assisting customers migrating to the v3 API where they are able to efficiently and sooner than if they need to interact more with support to get explanations as to what calls are utilized for in the application.

As v3 was originally deployed as a DI interface and has changed use cases to an overall API endpoint for use moving forward this seems like something that should be added and maintened moving forward as the understanding is v2 is desired to be disabled at some point in the future.

Idea priority High