此内容没有您所选择的语言版本。

Chapter 5. Provisioning Rate Limits


Rate limits allow you to throttle access to your API resources. You can configure different limits for separate developer segments through the use of application plans.

Once you have rate limits in place, these limits will control the responses a developer receives when they make authorization request calls to the 3scale back end.

5.1. Step 1: Go to the application plan

If you do not have an application plan defined yet, create one first. Otherwise, select the plan you want to set rate limits for and click edit.

5.2. Step 2: Set the rate limits

5.3. Step 3: Update the application plan

When you are finished setting the limits you require, save your changes by clicking Update Application plan.

5.4. Step 4: Put the new rate limits into action

Now that you have your rate limits defined, the following will happen:

  • If you have alerts configured, the new limits will be used to decide when notifications are sent.
  • When you make authorization calls to the 3scale back end, the limits will be taken into account and the response will be with status code 409. In this case the APIcast API gateway sends a response to the client with the status code 429 Too Many Requests and the message, Limits exceeded.

Once your rate limits are operational, you will see the users who are reaching the limits on your dashboard, making it quick and easy to check for potential plan upgrade candidates.

Note

For more information about soft and hard limits, you should read 1.1.3.2. Configure your API access policies with application plans, window="_blank" in our Quickstart guide.

5.5. More information

Besides setting rate limits, you can also set variable pricing rules for the same metrics – see provision paid plans

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat