Skip to Main Content
Cloud Management and AIOps
Hide about this portal


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.

Implement user role restriction to view specific API endpoints on the Swagger API docs page (v3)

See this idea on ideas.ibm.com

Use-case to separate certain access to only accounts we assign. We would like to limit the amount of accounts that are available to generally get web requests to those with the appropriate permission. Where we can establish who can use GET requests (still based on user access) and then the privileged access for UPDATE, DELETE, CREATE, etc.

In example, all users (about 800ish) with a general access view can today decide to just run an API v3 get request to the platform, without restriction. If more than a few people requested tables that were larger than normal such as entire device lists or even an unfiltered object list, this could impact the performance of our Cluster Master. We would like to limit our requests from known accounts.

While data is still restricted by user role access, overall attempts at the API are not restricted.

Idea priority Medium