自
2025 年 9 月 8 日起，每個新委刊項都必須聲明是否會放送歐盟政治廣告。如果透過 Display & Video 360 API 和 SDF 上傳的檔案未提供聲明，系統就會失敗。如要進一步瞭解如何更新整合服務以進行這項聲明，請參閱
淘汰項目頁面。
使用限制
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
使用限制可避免 Google 基礎架構在自動化流程中使用 Display & Video 360 API 的方式不當。確保單一開發人員的行為不會對更廣大的社群造成負面影響。
API 要求配額限制
Display & Video 360 API 使用兩種限制：
- 總配額限制：所有相關要求都會計入。
- 寫入配額限制：所有針對寫入方法提出的相關要求都會計入。寫入方法是指用於修改資源的方法，例如
create、patch、delete 或 bulkEdit。請注意，某些方法會比其他方法消耗更多寫入配額。
如果專案超出上述任一限制，可能會發生調節現象。
專案層級配額限制
下列預設配額限制適用於所有 Display & Video 360 API 資源和方法：
- 每項專案每分鐘的總要求數：
1500
- 每項專案每分鐘的寫入要求數：
700
廣告主專屬的請求配額限制
在要求網址中指定廣告主 ID 的方法，會計入額外的「每個專案的廣告主」配額限制。
所有網址路徑中指定廣告主 ID 的要求 (例如 advertisers.lineItems、advertisers.creatives 或 advertisers.channels 服務) 都會計入以下配額限制：
- 每個廣告主在每個專案中每分鐘的總請求數：
300
- 每個廣告主每項專案每分鐘的寫入要求數：
150
寫入密集方法
下列 API 方法會大量寫入，也就是說，這些方法會使用大量產品資源，因此會比其他寫入要求消耗更多寫入要求配額。
計算寫入要求配額用量時，系統會將針對寫入密集方法提出的要求計為 5 次寫入查詢。舉例來說，如果在 1 分鐘內提出 100 個標準寫入要求和 21 個寫入密集要求 (均未指定廣告客戶)，系統會將其計為 205 個寫入查詢 (100 + (21 * 5) =
205)，並超過現有的一般要求配額限制 (每分鐘 200 個寫入查詢)。
下列方法會大量寫入資料：
超出配額限制
如果您的要求因超出 API 要求限制而失敗，API 會傳回 HTTP 狀態碼和錯誤原因。此外，回應主體會詳細說明導致錯誤的原因。
下表列出因超出 API 要求限制而導致要求失敗的可能錯誤和建議動作。
| 程式碼 |
單次點擊收益 |
訊息 |
建議做法 |
429
|
RESOURCE_EXHAUSTED
|
資源已用盡 (例如檢查配額)。 |
請透過 Google API 控制台檢查您的用量，並修改工作流程，以便更有效地並行處理不同廣告客戶提出的要求，或更普遍地降低傳送要求的頻率。 |
您無法要求提高 Display & Video 360 API 配額限制。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eDisplay & Video 360 API usage is subject to quota limits to protect Google's infrastructure and ensure fair usage.\u003c/p\u003e\n"],["\u003cp\u003eTwo main quota types exist: total requests and write requests (methods modifying resources), with limits applied per project and per advertiser per project.\u003c/p\u003e\n"],["\u003cp\u003eCertain write-intensive methods consume more write quota than others.\u003c/p\u003e\n"],["\u003cp\u003eExceeding quota limits can lead to request throttling, indicated by a 429 error code, requiring adjustments to request frequency.\u003c/p\u003e\n"],["\u003cp\u003eQuota limit increases for the Display & Video 360 API are not available.\u003c/p\u003e\n"]]],[],null,["# Usage Limits\n\nUsage limits protect Google's infrastructure from automated processes that use\nthe Display \\& Video 360 API in an inappropriate way. They ensure that one developer's\nactions can't negatively impact the larger community.\n\nAPI request quota limits\n------------------------\n\nThe Display \\& Video 360 API uses two types of limits:\n\n- **Total quota limits**, which all relevant requests count against.\n- **Write quota limits** , which all relevant requests made to write methods count against. Write methods are defined as methods---such as `create`, `patch`, `delete`, or `bulkEdit`---that modify resources. Note that [some\n methods](#write_intensive) consume more write quota than others.\n\nIf your project exceeds any of these limits, [throttling could\noccur](#exceeding_limits).\n\n### Project-wide quota limit\n\nThe following default quota limits are shared by all Display \\& Video 360 API resources\nand methods:\n\n- **Total requests per minute per project:** `1500`\n- **Write requests per minute per project:** `700`\n\n### Advertiser-specific request quota limits\n\nMethods that specify an advertiser ID in the request URL count against\nadditional \"per advertiser per project\" quota limits.\n\nAll requests with an advertiser ID specified in their URL path---such as\nthose to the [`advertisers.lineItems`](/display-video/api/reference/rest/current/advertisers.lineItems),\n[`advertisers.creatives`](/display-video/api/reference/rest/current/advertisers.creatives), or\n[`advertisers.channels`](/display-video/api/reference/rest/current/advertisers.channels) services---will count against\nthe following quota limits:\n\n- **Total requests per minute per advertiser per project:** `300`\n- **Write requests per minute per advertiser per project:** `150`\n\nWrite-intensive methods\n-----------------------\n\nThe following API methods are write-intensive, meaning that they use a\nsignificant amount of product resources and, as a result, consume more\nwrite request quota than other write requests.\n\nRequests made to write-intensive methods are counted as 5 write queries\nwhen computing write request quota consumption. For example, 100 standard write\nrequests and 21 write-intensive requests (none of which specify an advertiser)\nmade within a minute would be counted as 205 write queries (`100 + (21 * 5) =\n205`) and would exceed the existing general request quota limit of 200 write\nqueries per minute.\n\nThe following methods are considered write-intensive:\n\n- [`customBiddingAlgorithms.scripts.create`](/display-video/api/reference/rest/current/customBiddingAlgorithms.scripts/create)\n- [`customBiddingAlgorithms.uploadScript`](/display-video/api/reference/rest/current/customBiddingAlgorithms/uploadScript)\n- [`firstPartyAndPartnerAudiences.create`](/display-video/api/reference/rest/current/firstPartyAndPartnerAudiences/create)\n- [`firstPartyAndPartnerAudiences.editCustomerMatchMembers`](/display-video/api/reference/rest/current/firstPartyAndPartnerAudiences/editCustomerMatchMembers)\n- [`media.upload`](/display-video/api/reference/rest/current/media/upload)\n\nExceeding quota limits\n----------------------\n\nIn the unlikely event that your request fails due to exceeding an API request\nlimit, the API returns an HTTP status code and reason for the error.\nAdditionally, the body of the response contains a detailed description of what\ncaused the error.\n\nThe following list shows the possible errors and recommended actions for\nrequest failures caused by exceeding API request limits.\n\n| Code | RPC | Message | Recommended Action |\n|-------|----------------------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `429` | `RESOURCE_EXHAUSTED` | Resource has been exhausted (e.g., check quota). | [Examine your usage](//console.developers.google.com/project/_/apiui/apiview/displayvideo.googleapis.com/metrics) from the Google API Console and modify your workflow to better parallelize requests made under different advertisers or more generally slow down the rate at which you are sending requests. |\n\nIncreases cannot be requested for Display \\& Video 360 API quota limits."]]
