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 Jul 13, 2020

Rate limit is not persistent so setting would be lost during system maintenance

API Connect V5 on-premise version has rate limit setting option for protecting backend service.
But this data is not persistent disappears when customer did some maintenance work, e.g. patch, PM etc.
As a result customer should calculate API call counts manually and cause huge inconvenience.

Idea priority Urgent
RFE ID 143885
RFE URL
RFE Product IBM API Connect
  • Guest
    Reply
    |
    Jun 14, 2023

    This also applies to v10 and our platform users are complaining, that the rate limit feature does not work as expected:

    we have customers, that use product plans and quotas to implement what we call a "package based billing model". API consumers subscribe to a plan and are allowed to invoke the API e.g. 1mio times per month and they pay for this volume of API calls. This can be configured as a hard limit, so API providers can rely on the gateway preventing consumers to use the API more often than ordered (using a hard limit).

    If there are maintenance operations, that reset these counters, API providers cannot rely on the gateways enforcing the quota and API consumers can invoke the API more often than they have paid for which can result in a loss of revenue for API providers.

    Please fix