Skip to Main Content

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:

Post your ideas

Start by posting 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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit



API Connect

Showing 442 of 1797

JSON Parser limits must apply by default to JSON response

JSON Parser limits must apply by default to JSON response as well. Need an option to override those values using some variables at API level.
8 months ago in API Connect 0 Future consideration

Limit CPU Consumption of API Connect componentes in Kubernetes Clusters to stay below purchased licenses

We use API Connect (including API Gateway) components in Kubernetes Clusters. we have purchased a certain amount of licenses (VPCs/PVUs). Currently there is no way to definie API Connect deployments to use no more CPUs than defined (for example: n...
about 2 months ago in API Connect 0 Submitted

Documentation on all severity levels and its syslog messages from all APIC components - (API Manager, Analytics, Developer Portal, and Gateway).

It would be useful to have documentation on what messages APIC sends out on all severity levels and on all components (GW, Manager, Analytics). The main purpose is monitoring and setting up better instructions on different levels of alarms. e.g WA...
about 2 months ago in API Connect 0 Submitted

Add certificate subject validation option to Crypto Validation Credentials

When setting up communication over insecure channels (i.e. over Internet) it is required to narrow down list of clients that might connect to DataPower. Selection based on validation against CA is too broad. It sohuld be narrowed down to be based ...
8 months ago in API Connect 0 Future consideration

Proxy server support in API Connect v2018

Using APIC 2018.4.1.10 on VMware in an on-premise environment, we are encountering connectivity issues towards external dependencies. It's a corporate policy to route all traffic requiring Internet access through a central proxy. This requires API...
almost 2 years ago in API Connect 0 Future consideration

Two Factor Authentication

It will be good if we have Two Factor Authentication on API Portal, we have corporate customer using our portal and security team ask for more authentication. Like, Google Authenticator, VASCO... Thanks
5 months ago in API Connect 3 Functionality already exists

stripe tax information / VAT

Currently, no tax information is output in the checkout process. Here the input of the VAT rate is required, as well as the output in the checkout process and the passing on to Stripe.
4 months ago in API Connect 0 Future consideration

Going back from an item, you shouldn't get the first page of the list

On v2018, when you are editing an object (API, application, product, etc.) and going back using the interface arrow, the browser returns to the first page of the item list. It would be desirable to go back to the same page number that you was view...
over 2 years ago in API Connect 0 Future consideration

OAuth support for GraphQL

Currently only client ID and/or secret is oficially supported for GraphQL APIs. Most of the users will want to replicate the same security on to the REST and GraphQL APIs.
11 months ago in API Connect 0 Future consideration

Adding existing user, who has no association yet, as member of catalog or space without invitation

This is related to case: TS005102904 Currently, it is not possible to add an existing user by REST API from user registry as catalog or space level members, if the user does not yet have an association in p-org level. Since the user already exists...
11 months ago in API Connect 1 Not under consideration