Rate Limit

2.1.0 (DataPower API Gateway Version 10.0.1.0 or later)

2.2.0 (DataPower API Gateway Version 10.0.2.0 or later)

2.3.0 (DataPower API Gateway Version 10.5.0.0

The default value is ratelimit.

• Catalog by Name: the limits to be applied are defined in the appropriate api-collection object on the DataPower API Gateway, which is the object that represents your API Connect Catalog in the gateway configuration.

  For details of how to configure a rate, burst, or count limit in the api-collection object, see Configuring a rate, burst, or count limit on the.

• Plan by Name: the limits to be applied are assembly burst limits or assembly count limits defined on the Plan to which the calling application is subscribed. For details on how to configure assembly burst limits and assembly count limits in a Plan, see Editing a draft Product.
  Note: The following conditions apply to a Plan by Name rate limit policy:

  • Every Plan that contains the API that is being limited must have the named rate limit applied.
  • A Plan by Name rate limit policy cannot be used with automatically generated Products.
• Gateway by Name: the limits to be applied are defined in the apigw object, named apiconnect, on the DataPower API Gateway gateway.

  For details of how to configure a rate, burst, or count limit in the apigw object, see Configuring a rate, burst, or count limit on the.

• Plan Default: the rate and burst limits that are applied are the default ones configured in the Plan to which the calling application is subscribed. For details on how to configure default Plan rate and burst limits, see Editing a draft Product.
  Note: The use of this option does not disable any automatic preflow rate limit policy that might be in place, and could result in the application of the rate limiting being repeated. For more information on preflow policies, see Customizing the preflow policies.

To display the Rate Limit Name field, click Add Rate Limit; you can add as many rate limits as you want.

¹You must provide at least one rate, burst, or count limit.

If Source is set to Plan by Name, the name of an assembly burst limit in a Plan.

To display the Burst Limit Name field, click Add Burst Limit; you can add as many burst limits as you want.

²You must provide at least one rate, burst, or count limit.

If Source is set to Plan by Name, the name of an assembly count limit in a Plan.

To display the Count Limit Name field, click Add Count Limit; you can add as many count limits as you want.

³You must provide at least one rate, burst, or count limit.

• Consume: the policy reduces the balance of available requests that remain in the interval defined by the rate limit specified in the Rate Limit Name field.

  The amount by which the remaining balance is reduced is the value that results from the weight expression defined in the specified rate limit.

• Replenish: the policy increases the balance of available requests that remain in the interval defined by the rate limit specified in the Rate Limit Name field.

  The amount by which the remaining balance is increased is the value that results from the weight expression defined in the specified rate limit.

  The purpose of the replenish operation is to restore an appropriate amount of remaining balance in cases where the amount calculated by an earlier consume operation turns out to be too high. For example, for an assembly rate limit with a limit of 100, a consume operation with a weight of 60 uses 60 requests, leaving 40 requests remaining for the interval. If the weight expression in the subsequent replenish operation computes to 15, meaning that the weight expression calculated that the actual request usage was only 45, the replenish operation increases the remaining requests by 15, to a remaining balance of 55.

  Note that the replenish operation cannot increase the remaining requests allowed beyond the original limit defined in the assembly rate limit scheme. In this example, a replenish operation cannot replenish requests beyond 100. A replenish operation is skipped if the weight expression evaluates to a value of less than 1.

  The default value is Consume.

By default, the count limit is automatically decremented at the end of the API assembly by the total amount incremented during the assembly, minus any decrement operations that are defined in the assembly. You do not need to explicitly define decrement operations unless you want the decrements to occur at specific points in the assembly. However, if the auto decrement feature has been explicitly disabled in the count limit configuration, you must include a corresponding decrement operation, otherwise when the count limit is reached all future calls are blocked. For more information on configuring a count limit, see Configuring a rate, burst, or count limit on the.

The default value is Increment.

For a burst limit, the only option is Consume, meaning that the limit applied is that defined in the burst limit specified in the Burst Limit Name field.