Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Submitted
Workspace Db2
Created by Guest
Created on Jul 2, 2026

Request for REST API Documentation Coverage and Consistency Improvements

Request

we would like to raise the level of detail and documentation coverage of the REST APIs to be comparable to that of the Java SDK documentation, which is relatively comprehensive within the same API documentation set.

Why useful

The current REST API documentation lacks sufficient information regarding expected responses, error handling behavior, valid parameter values, and common API conventions. 

When documentation does not explicitly define API behavior, clients are forced to determine behavior through testing and observation. Over time, these observed behaviors may be treated as part of the API contract, even when they were never intended or documented. 


Desired Documentation Improvement Direction and Level of Detail
Detailed findings, recommended documentation examples, and prioritization have been compiled in a separate document, and an English version is already available for direct sharing with the overseas development team. (See atached file)

Needed By Quarter