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

Status Future consideration
Workspace API Connect
Created by Guest
Created on Feb 10, 2021

API Connect Financial-grade API compliant

In the banking customer, Financial-grade API (FAPI) compliant is requested.
API Connect have some capability for FAPI specification, but it is not full.
OpenID FAPI certification is required.

Idea priority Medium
Use Case
The bank customer must have a protected API environment. As a secure API to be used in the financial industry, Financial-grade API specification has been developed and compliant is being requested by banks. Financial-grade API (FAPI)
RFE ID 148527
RFE Product IBM API Connect
  • Guest
    Nov 26, 2021

    We (CosmosDirekt) as an german insurance company and user of the API Connect product strongly support this feature request. We have the requirement to secure our APIs as good as possible, since we are processing personal and confidential data.

    From our point of view the currently supported OAuth flows supported by the product (especially OAuth Client Credentials Flow with clientID and secret) are not sufficient to cover our regulatory requirements. From our point of view we would like to implement OAuth Client Credentials Flow with private-key-jwt. As you see in the FAPI standard this is also part of the AdvancedSecurity Profile - so this gives us the opportunity to adequately secure high-risk APIs. Even if the product does not fully support all client authentication methods described in the FAPI standard, at least the private_key_jwt support would be a very important asset. Thanks for taking that into consideration!

    Regards, Thomas Matal