Display & Video 360 API v1 has been sunset and requests made to it could return an error. You must use Display & Video 360 API v2 instead.

For v1 to v2 migration instructions, see our migration guide.

Usage Limits

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 cannot negatively impact the larger community.

API request quota limits

Display & Video 360 API request quotas vary depending on the resource and method.

Requests to Display & Video 360 API methods count against one of two quota buckets:

  • Methods that specify an advertiser ID in the request URL count against "per advertiser per project" quota limits.
  • All other methods count against general "per project" quota limits.

In addition, each of these buckets have the following two types of limits:

  • A Total quota limit, which all relevant requests count against.
  • A Write quota limit, 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.

If your project exceeds any of these limits, throttling could occur.

Advertiser-specific request quota limits

All requests with an advertiser ID specified in their URL path—such as those to the advertisers.lineItems, advertisers.creatives, or advertisers.channels services—will count against the following quota limits:

  • Total requests per minute per advertiser per project: 300
  • Write requests per minute per advertiser per project: 150

General request quota limit

All requests that do not specify an advertiser ID in their URL path—such as those to the partners, sdfdownloadtasks, or targetingTypes.targetingOptions services—will count against the following quota limits:

  • Total requests per minute per project: 600
  • Write requests per minute per project: 200

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:

Exceeding quota limits

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.