Consider the following rules and guidelines when you work with API groups:
•You can group different operations from different published APIs. You can view the operation-level polices applied to each operation.
•You can add only one operation with the same operation type and operation endpoint to one API group.
•After you delete an API operation from an API group, save the API group to successfully remove the operation from the API group. Otherwise, the API operation is not removed from the API group.
•After you create and save an API group, if any associated authentication policy changes any operation in that API group, you must add the operations again for the policies to take effect. Authentication policies doesn't refresh automatically for any operation in an API group.
•If you associate a rate limit policy at the API level, operations level, and user level, the rate limit policy with the minimum value takes precedence and the other values are ignored.
•If you associate an API-level rate limit policy with an API, but do not assign policies to individual API operations, the API-level rate limit policy is automatically applied to the operations when you add the published API operation to an API group. The active managed API groups also enforces the applied rate limit.