Skip to main content
In this scenario, the application of the API Based Throttling policy to a Mock API created on Apinizer will be tested. Using throttling for services is a method of limiting the number of requests by preventing overload. In the scenario, we can ensure that only 10 requests are accepted every 5 minutes by dividing incoming requests into equal 5-minute time intervals. Let’s create a Mock API example and add the policy. Generate JWK Screen We add API Based Throttling as a policy. Generate JWK Screen In the scenario, let’s limit incoming requests to 10 requests in 5 minutes using the Fixed Window (Fixed Window) method.
  • If the period is set to 5 minutes and for example the policy was saved at 12:00:00:
  • Requests between 12:00:00 and 12:04:59 are counted in the same window.
  • At 12:05:00, a new window starts and the counter resets.
Generate JWK Screen
FieldDescription
Show Rate Limit Statistics in Response HeaderIf activated, shows rate limit statistics in the response header.
Permitted Message CountThe number of requests allowed. We set this to 10 in this scenario.
Interval Time AmountThe period determined according to the selected time unit. We set this to 5 in this scenario.
Interval Time UnitTime unit. We set this to minute in this scenario.
Target-Specific Throttling RulesSpecial throttling limits are defined for each target.
Interval Window TypeMethod used to apply the time interval. 5-minute time periods in Fixed type.
Cache Connection Timeout (Second)Specify the connection timeout value for the connection between the policy and cache.
Action for Cache Connection ErrorIf there is a connection problem with cache, it is determined whether to return an error (Fail is selected) or continue without applying the request limit (Continue is selected).
When we send a sample request from the test console, the message was blocked because the restriction limit was reached after the 10th request within the time range between 14:00:00 and 14:04:59 at the current time. Generate JWK Screen

​
Target-Specific Throttling Rules (Target-Specific Throttling Rules)

Thanks to this feature, you can define special throttling limitations for specific users or targets. We add API Based Throttling as a policy. Generate JWK Screen
  • Using Target-Specific Throttling Rules (Target-Specific Throttling Rules), special quota limits can be determined based on users (based on header, body, or another field). While limiting incoming requests to 100 requests for 5 minutes using the Fixed Window (Fixed Window) method in the general policy, a limit of maximum 5 requests in 5 minutes can be defined for the user1 user at the same time.
  • In the Fixed Window method, if the period is set to 5 and minute is selected:
  • For example, if the policy was saved at 12:00:00, this policy will be valid between 12:00:00 and 12:04:59 within the current day, and 100 requests can be made as a general rule during this period.
  • For the user1 user we defined with Target-Specific Quota Rules, a minute-based limit has been determined. If a 5-minute period starts at 12:00:00, this covers the period between 12:00:00 and 12:04:59, and the user1 user can make a maximum of 5 requests in this time range. In the next 5-minute period (12:05:00), the counter resets.
  • In the next 5-minute period (for example between 12:05:00 and 12:09:59), while a new 100 request right is defined for the general policy, 5 request rights will be redefined for the user1 user as well.
Generate JWK Screen When we send a sample request from the test console, when we send a request with the user1 user from the username Header, the message was blocked because the restriction limit was reached after the 5th request within the time range between 12:00:00 and 12:04:59 at the current hour. Generate JWK Screen