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 DataPower Gateway
Created by Guest
Created on Mar 4, 2026

We would like for traditional DataPower services to support JSON RFC 7159 when setting request and/or response type to JSON

At the moment the request and response type settings in traditional DataPower services like Multiprotocol Gateway and Web Service Proxy support JSON RFC 4627 when choosing request and/or response type JSON. For more recent services with a JSON payload DataPower does not accept a JSON message when it is valid according to RFC 7159 but not according to RFC 4627. 
We know that it is possible to build a workaround, but then the value of setting the request and response type to JSON is lost. 
We think it would benefit everyone who is using DataPower traditional services to support REST services with JSON content. 

Idea priority High