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 Not under consideration
Categories Event Processing
Created by Guest
Created on Sep 12, 2024

API optional Variable Handling

When invoking an API request in the Event Processing flow we need additional ability to map optional request variables the request header and body that may not be defined in the OpenAPI Spec.

Idea priority Low
  • Admin
    Sam Kunthiparambil
    Reply
    |
    Sep 17, 2024

    Thank you for the idea. The team has discussed and reviewed this piece of work.
    We have been given to understand that for the ability to map optional parameters that are not defined in the OpenAPI spec, client is using some APIs that are configured with some additional parameters that are not defined in the published OpenAPI spec for these APIs. They can notably add for example the parameter useStage=true to target the stage instance. They are currently using other tools to consume their APIs where they can define all the parameters by using the UI and they would like to have a similar feature in EP.

    The team has decided that this is something that we would like to implement as of now, in comparison to the other high urgency items in line. As a workaround, the client has been advised that currently they should edit the file containing the OpenAPI spec and add by themselves the missing optional parameters before uploading the file to EP.


    Marking this idea as not under consideration.