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.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on Nov 19, 2024

RELATED IDEAS

Make HTTP Input parsing for RESTAPI's dynamic based on provided path request body

# Issue


When creating a new REST API, the parsing setting on the generated HTTP Input node of the generated message flow defaults to JSON.


## Description


When creating a REST API, we can specify multiple paths, operations, and request bodies. However, the parsing on the HTTP Input node for the generated message flow always defaults to JSON.


It would make more sense for the parsing setting to align with the request body or request bodies provided for that API:


- **Only JSON request body** → JSON parsing.

- **Only XML request body** → XML parsing.

- **Mixed request bodies** → BLOB parsing.


## Solution


Update the REST API generation code to follow the `requestBody` definitions.


Idea priority High
  • Admin
    Ben Thompson
    Reply
    |     Nov 29, 2024

    Thank you for taking the time to raise this enhancement request. Although the original design intention for REST APIs was centred around JSON inputs, we do have a documentation page describing how the message flow can be adapted to deal with non-JSON data ...


    https://www.ibm.com/docs/en/app-connect/13.0?topic=apis-handling-non-json-data-in-rest-api


    Having noted this, we like the idea of an extra configuration option on an HTTPInput node to infer message parsing settings from the HTTP Content-Type. We have a similar option on the RESTRequest node's Response Message Parsing tab ("Automatic Content-type handling"). If such an option existed on HTTPInput, then this could then be set (as a new non-default configuration option, in order to preserve back compatability) when the REST API top level message flow is generated. Status of the idea is updated to Future Consideration.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.