Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 Submitted
Workspace App Connect
Created by Guest
Created on Mar 5, 2026

Feature Request: Extend OpenAPI Support to 3.1.1 Across All Outbound REST Nodes in IBM ACE

BM App Connect Enterprise V13 already supports OpenAPI 3.0 for inbound REST API definitions. We now request an extension of this existing support to cover OpenAPI 3.1.1 — the current stable and recommended version of the specification — specifically across all outbound REST nodes.

Affected nodes:

The following three nodes currently accept only a Swagger 2.0 definition file when configuring the target external API, and should be extended to support OpenAPI 3.1.1:

  • RESTRequest node — used to issue synchronous requests to external REST APIs
  • RESTAsyncRequest node — used to initiate asynchronous requests to external REST APIs
  • RESTAsyncResponse node — used to receive the asynchronous response, paired with the RESTAsyncRequest node

All three nodes rely on an attached API definition file to determine endpoint URL, path, operation, and parameter encoding. Today that file must be in Swagger 2.0 format. We request that OpenAPI 3.1.1 documents be accepted as a valid alternative in all three nodes.

Why 3.1.1 specifically: OpenAPI 3.1.1, released in October 2024, is the OpenAPI Initiative's current recommended version for all new and upgraded projects. Key improvements over 3.0 include full JSON Schema 2020-12 alignment, native webhook support, improved schema expressiveness, and enhanced security scheme definitions — all of which appear regularly in modern third-party API specifications that ACE customers need to consume.

Business justification: Customers are increasingly receiving API specifications from partners and vendors in OpenAPI 3.1.x format. Without native support in the RESTRequest, RESTAsyncRequest and RESTAsyncResponse nodes, integration teams are forced to manually downconvert these specs to Swagger 2.0 — a process that is error-prone, time-consuming, and unsustainable at scale. Since the OpenAPI 3.0 parsing infrastructure already exists in ACE V13, extending it to cover 3.1.1 on the outbound side represents an incremental and well-justified improvement.

 

 

 

 

 

Idea priority Medium