Hello,
We are currently transitioning from Apigee Edge to Apigee X and have encountered an issue with the rate plan configuration. In Apigee Edge, we were able to limit the total number of monetized API calls to a specific number for developers onboarded with the POSTPAID billing type. Once the number of transactions exceeded the limit, the MonetizationLimitsCheck policy would block further API calls with a custom error that we configured into the policy.
However, in Apigee X, we found that we cannot restrict the number of API calls in the rate plan configuration. It is open-ended.
The recommendation provided in the documentation is to use the Quota policy to read the quota configured on the API Product (Reference).
We’ve tried this approach, but it does not work when we have multiple API proxies bundled into an API Product. The quota counters are maintained within an API Proxy, and we could not find an option to maintain a shared counter across API Proxies in a Product.
One workaround suggested in the community is to use separate API Proxies for the purpose of counting alone (Reference). However, this solution results in doubling the number of API transactions in Apigee, which is not ideal.
We are looking for a more straightforward approach to resolve this problem. Any suggestions or guidance would be greatly appreciated.
Thank you in advance for your help.