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 Future consideration
Workspace API Connect
Created by Guest
Created on May 11, 2020

API Connect: Add support for custom parameters in product plans

Currently, only the transaction rate can be set up in an API product plan. We have a use case where a consumer is allowed to submit attachments up to a certain size, based on a subscribed (and approved) plan. Since there is no way to do this today, we have a workaround where we set up a soft transaction limit with a precise name - max-attachment-size. We added an XSLT transformation into the API assembly to pick this value based on the name - max-attachment-size - up from the subscribed plan and add it as a parameter to the HTTP request. The backend service receiving the request will enforce the header. A side effect of it is that the max-attachment-size limit appears as a traffic limit on the API Developer portal instead of being described for what it is - message size limit.

We would like the ability to set up a custom parameter that gets added as a custom HTTP header and can be enforced by a backend service. The parameter role (i.e max message size) should be displayed correctly in the API Developer Portal.

Idea priority High
RFE ID 142317
RFE URL
RFE Product IBM API Connect