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 Under review
Workspace API Connect
Created by Guest
Created on Jun 5, 2025

APIC SaaS to support V1 AWS API Gateway Payload format along with v2 payload format while converting the request from Restful to Event format with Lambda Policy

Currently with Lambda policy in APIC SaaS, while converting the payload format from REST to Event and Vice versa, the policy is following AWS API Gateway V2 Payload format conversion.

Lot of existing Lambda's onboarded would be following V1 Payload format and could have an issue when trying to connect through Lambda Policy instead of AWS API Gateway due to Payload version mismatch. We might have to explicitly modify Legacy Lambda's to support new payload format and redeploy to remediate the issue.

Is it possible to allow both payload format conversion techniques and User can switch between both inside the APIC API flow based on the requirement?

Idea priority Urgent