[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-11。"],[[["\u003cp\u003eYou can limit API requests by setting caps on requests per day, per minute, or per minute per user to manage usage and billing.\u003c/p\u003e\n"],["\u003cp\u003eAPI quota limits can be viewed and modified in the Google Cloud console, within the APIs & Services Dashboard or the Quotas page.\u003c/p\u003e\n"],["\u003cp\u003eSome APIs allow for higher quota limits if billing is enabled on the project, and you can request higher limits by submitting a form.\u003c/p\u003e\n"],["\u003cp\u003eTo prevent overuse by individual users, certain APIs offer a default per-user per-minute limit, which can be modified, and users can be identified via the \u003ccode\u003equotaUser\u003c/code\u003e parameter.\u003c/p\u003e\n"],["\u003cp\u003eWhen setting up quota limits as a tool to manage billing, remember that quota limits are not exact and will need some buffer room.\u003c/p\u003e\n"]]],[],null,["# Capping API usage\n\nDepending on the API, you can explicitly cap requests by limiting the\n*requests per day* , *requests per minute* , or *requests per\nminute per user*.\n\nYou might want to limit the billable usage by setting caps. For example, to\nprevent getting billed for usage beyond the free courtesy usage limits, you can\nset requests per day caps.\n| **Important:** Quota limits are not always entirely precise, because there is some latency between when a quota is surpassed and when the enforcement begins. When using quota as a tool to limit billing, allow some buffer.\n\nView and modify the limits on the number of requests\n----------------------------------------------------\n\nYou can set limits to all requests to any billable API. Most APIs set default\nlimits, but you can change that limit up to a maximum specified by Google.\nSome APIs set a low limit until you\n[enable billing on your project](/billing/docs/how-to/modify-project).\n\nTo view or change the limits for your API, do the following:\n\n1. In the Google Cloud console, go to the **APIs \\& Services Dashboard** page.\n\n [Go to APIs \\& Services Dashboard](https://console.cloud.google.com/apis/dashboard?project=_)\n2. From the projects list, select a project or create a new one.\n3. Click the name of the API you're interested in.\n4. Click **Quotas** . If the **Quotas** tab is not present in the tab nav, it means the API you've selected doesn't have quotas defined.\n5. To find the quota you want to cap, enter the appropriate properties and values in the filter_list **Filter** field. For example, to find the **Subnetworks** quota, enter **Quota:Subnetworks**.\n6. Click the checkbox next to the quota you want to cap, and then click create **EDIT QUOTAS**.\n7. Complete the quota change form, including the new limit that you want to set.\n8. Click **SUBMIT REQUEST**.\n\nSome APIs let you request a higher limit by submitting a form. Some\nAPIs let you specify a higher quota only if\n[billing is enabled on the project](/billing/docs/how-to/modify-project).\n| **Note:** You can set daily billable limits only on billable APIs, and in some cases, only if billing is enabled on your project. If your project doesn't use any billable APIs, then you can't set daily limits. [Learn more about billing accounts](/billing/docs/how-to/manage-billing-account).\n\nThe Premium Plan quota sections pertain to the\n[Google Maps Premium Plan](https://developers.google.com/maps/premium), which\nis no longer offered. Unless you are a current Google Maps Premium plan\ncustomer, don't edit those sections.\n\nLimiting requests per user\n--------------------------\n\nTo prevent individual users from using up your API quota, some APIs include a\ndefault per user per minute limit.\n\nTo check if your API includes a default per user per minute limit, look for it\nin your API quotas as described in the instructions for\n[View and modify the limits on the number of requests](#modify).\nIf such a default limit exists for that API, you can modify that value to limit\nthe quota available to each user by following the steps in these instructions.\nIf your API does not include this default limit in its quotas, adding or\nmodifying it is not supported.\n\nIndividual users are identified by a unique string. If you're creating a\nserver-side application (where the calling code is hosted on a server that you\nown) that makes requests on behalf of users, your requests to the API that\nyou're limiting usage for must include the `quotaUser` parameter. This parameter\nis defined in the [System parameters](/apis/docs/system-parameters) documentation.\n| **Note:** Although per-user limits are specified in queries per minute, we permit short-term usage spikes. Therefore, you should set your limits based on sustained average traffic levels. If anyone tries to use an API in excess of these settings, the requests will trigger a *limit exceeded* error.\n\nTo identify a user, use the `quotaUser=userID` URL query parameter. This value\nis for short-term quota enforcement only, so you don't need to use a real user\nID. You can choose any arbitrary string under 40 characters long that uniquely\nidentifies a user.\n\nThe `quotaUser` parameter is only used for capping requests per user per\nminute. If you don't send the `quotaUser` parameter, then all calls are\nattributed to your server machines, in which case calls can't be capped by user.\n\nIf your API does not include a default per user per minute limit, then\n`quotaUser` values are ignored.\n| **Important:** When sending any user identifier, be sure that you comply with any local laws, including any laws relating to the disclosure of any personal information you send with each request. Best practice is to include as little personal information as possible.\n\nView and edit all quotas for APIs in a project\n----------------------------------------------\n\nYou can review, edit, and request higher quota limits for all billable APIs in\na given project by viewing the **Quotas** page in the **IAM \\& Admin** section of\nGoogle Cloud console.\n\nTo view and edit quotas for all billable APIs in your project, do the following:\n\n1. In the Google Cloud console, go to the **Quotas** page.\n\n [Go to Quotas](https://console.cloud.google.com/iam-admin/quotas?project=_)\n2. From the projects list, select a project or create a new one. The **Quotas** page for the selected project displays, listing one line item for each type of quota available in each service.\n3. Click filter_list **Filter table** to query your quota by a specific property.\n4. Check the box next to the quota(s) you want to edit. Billing must be enabled on the project in order to click some of the checkboxes. If you prefer to edit all the quotas for a single API, click the name of the service to access the Quotas page for that API.\n5. Click edit **EDIT QUOTAS**.\n6. In the **Quota changes** pane that displays, expand the service view, then edit the quotas in that service as needed, and then click **DONE**.\n7. Repeat to edit the quotas in each of the selected services.\n - The current quota limits are pre-populated in the input boxes.\n - A service with an alert icon (error) on submission has input errors.\n - You can add more quotas to edit by selecting them as described before.\n - You can remove a service from the **Quota changes** pane by hovering over the unexpanded service view, and then clicking the delete icon (delete).\n8. When you are done editing quotas, click **NEXT**.\n9. If your quota edit request needs review, the **Contact details** form displays. Complete the form with your contact details.\n10. Click **SUBMIT REQUEST**."]]
