Starting September 8, 2025, every new line item will need to declare whether or not they will serve Eurpoean Union (EU) political ads. Display & Video 360 API and SDF uploads that don't provide declarations will fail. See our deprecations page for more details on how to update your integration to make this declaration.
Stay organized with collections
Save and categorize content based on your preferences.
Usage limits protect Google's infrastructure from automated processes that use
the Display & Video 360 API in an inappropriate way. They ensure that one developer's
actions can't negatively impact the larger community.
API request quota limits
The Display & Video 360 API uses two types of limits:
Total quota limits, which all relevant requests count against.
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
methods consume more write quota than others.
Total requests per minute per advertiser per project:300
Write requests per minute per advertiser per project:150
Write-intensive methods
The following API methods are write-intensive, meaning that they use a
significant amount of product resources and, as a result, consume more
write request quota than other write requests.
Requests made to write-intensive methods are counted as 5 write queries
when computing write request quota consumption. For example, 100 standard write
requests and 21 write-intensive requests (none of which specify an advertiser)
made within a minute would be counted as 205 write queries (100 + (21 * 5) =
205) and would exceed the existing general request quota limit of 200 write
queries per minute.
The following methods are considered write-intensive:
In the unlikely event that your request fails due to exceeding an API request
limit, the API returns an HTTP status code and reason for the error.
Additionally, the body of the response contains a detailed description of what
caused the error.
The following list shows the possible errors and recommended actions for
request failures caused by exceeding API request limits.
Code
RPC
Message
Recommended Action
429
RESOURCE_EXHAUSTED
Resource has
been
exhausted
(e.g., check
quota).
Examine your usage
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.
Increases cannot be requested for Display & Video 360 API quota limits.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-09 UTC."],[[["\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."]]
