The optimized targeting launch has been postponed. Line items will continue to use the targeting expansion feature and the targetingExpansion field of the LineItem resource will continue to behave as it has previously.

Usage Limits

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

API request quota

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

Total request quota

The following default API request limits are shared by all Display & Video 360 API resources and methods.

  • Queries per project per day: 172,800
  • Queries per minute per project: 1,200

Write request quota

The following default API request limits are shared by all Display & Video 360 API write methods. Write methods are defined as methods—such as create, patch, delete, or bulkEdit—that modify resources.

  • Write queries per minute per project: 600

Note that some methods consume more write quota than others.

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, 400 standard write requests and 41 write-intensive requests made within a minute would be counted as 605 write queries (400 + (41 * 5) = 605) and exceed the existing quota of 600 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 make fewer requests or slow down the requests or slow down the rate at which you are sending requests. You can request additional quota if you believe your usage is reasonable.

Requesting additional quota

If you think that your application requires additional daily quota, you can request more by following the instructions below.

  1. Navigate to the Display & Video 360 API in the Google API Console.
  2. Review your usage statistics from the Metrics page to ensure your application is behaving as expected. Pay close attention to the methods that have been called and address any unexpected or excessive usage before proceeding.
  3. If usage looks normal, navigate to the Quotas page, pick quota type you'd like to increase, click the edit icon next to Queries per day and then the link to Apply for higher quota.

Make sure to review the information and follow the instructions included in the quota request form before submitting an increase request.