Display & Video 360 API Quotas and Billing FAQs
Display & Video 360 API access is governed by project-level quotas, and API use does not have a separate per-request charge: the API is provided without an additional fee. Actual advertising costs, such as media spend and applicable platform fees, are separate from API access, while quota limits and billing settings can depend on the Google Cloud project and account setup.
What the API does and who can use it
The Display & Video 360 API lets authorized applications work with campaign resources, including advertisers, insertion orders, line items, audiences, and reports. It is intended for programmatic management and integration rather than replacing the Display & Video 360 interface in every workflow. Access requires an eligible Display & Video 360 account, API authorization, and a Google Cloud project with the API enabled. A user or service account also needs the relevant permissions in the Display & Video 360 partner or advertiser account.
These access requirements are distinct from quotas. Turning on the API does not guarantee that every account can access every resource, and having a large quota does not grant permission to read or change campaign data. Setup and eligibility details can change, so administrators should consult current Google documentation and their account representative when access is unavailable.
How quota limits work
Google applies usage limits to help maintain service availability. The relevant quota is associated with API usage and the Cloud project making requests; limits may also be enforced per user or through other documented controls. Quotas can include request-rate limits and daily usage limits. Their exact names, values, scope, and availability are subject to change, so there is no safe universal number of calls per day or per second to quote for every project.
One API call is not necessarily equivalent to one item processed. A list request may return multiple resources, while pagination may require additional requests. Some operations have different costs or constraints, and a report workflow may involve creating a query, checking its status, and retrieving results. Read the quota page for the specific API and project in Google Cloud Console, along with the current API reference, before designing around a limit.
For example, if an integration needs to inspect many line items, it should use supported page sizes and pagination rather than make one request per item when a collection endpoint can do the job. It should also avoid repeatedly fetching unchanged data. These choices reduce request volume and make the integration more resilient when quotas are tight.
Billing: API access versus advertising costs
There is no separate charge simply for making Display & Video 360 API requests. In particular, enabling the API or receiving a successful response should not be treated as a billable media impression or campaign action. The advertising activity managed through the API can, however, incur the ordinary costs associated with Display & Video 360 campaigns, according to the account’s commercial arrangements and applicable fees.
Google Cloud billing is a separate question. Cloud projects have billing accounts and billing settings for Cloud services, but the presence of a billing account does not itself mean the Display & Video 360 API has a per-call price. Check the API’s current pricing and quota documentation in the Cloud Console for any changes or project-specific requirements, and review campaign billing through the appropriate Display & Video 360 account channels. Do not infer media charges from API request counts.
In short, an API quota is a limit on use, not a price. If a project exceeds its quota, requests may be rejected or delayed; this is different from an invoice for extra calls.
Monitor usage and handle quota errors
Use Google Cloud Console’s API and services pages to inspect enabled APIs, credentials, and available quota metrics. The precise console labels and available metrics may vary. Also log request timestamps, method names, response status codes, and any returned error details in your application. Avoid recording access tokens or sensitive campaign data in logs.
When a request is rejected because of a rate or quota limit, use a controlled retry strategy rather than retrying continuously. A practical approach is to:
- Check the error response and confirm that the failure is actually quota-related, not a permissions or invalid-request problem.
- Pause before retrying, then increase the wait between repeated failures with exponential backoff and a small amount of random jitter.
- Respect any retry guidance included in the response, and cap retries so a persistent problem does not create an endless loop.
- Reduce unnecessary calls with pagination, caching where appropriate, and batching only where the API explicitly supports it.
- Review project quota metrics and request a quota adjustment through the documented Cloud Console process if the workload has a justified, sustained need.
A quota increase is not automatic and may be subject to review. It also does not fix a missing permission, a disabled API, an invalid credential, or an account that is not eligible for access.
Plan an integration responsibly
Before deployment, identify which project owns the API credentials and which Display & Video 360 partner or advertiser resources the application must access. Grant only the necessary permissions, protect credentials, and separate production from development use when practical. Estimate request volume from the actual workflow, including pagination, polling, retries, and scheduled jobs—not just the number of campaigns.
Polling is a common source of avoidable usage. For example, checking a long-running report every few seconds can consume calls without making the report finish sooner. Prefer sensible intervals, stop polling after a defined period, and handle incomplete or failed reports explicitly. Also make write operations safe to retry: before repeating a request after a timeout, determine whether the original operation might already have succeeded.
Keep a margin below the published limits. Traffic can be bursty, several users may share a project, and a temporary retry storm can multiply normal request volume. Monitor the application after changes to campaign volume or scheduling, and revisit Google’s current documentation because quota policies can evolve.
Common misconceptions and alternatives
Two misunderstandings cause frequent confusion. First, a quota is not a monthly allowance of free advertising: it governs API use, not campaign spend. Second, a successful OAuth sign-in does not automatically authorize every API operation; the signed-in identity still needs appropriate account access, and the application must use valid credentials for its intended access pattern.
If the API is unavailable or unnecessary for a task, an authorized user may be able to complete it in the Display & Video 360 interface. For recurring or large-scale work, the API can provide automation, but it brings responsibility for credential management, error handling, monitoring, and quota-aware design. Choose the interface or API based on the task and the permissions available, not on an assumption that one avoids advertising costs.
Frequently Asked Questions
Does the Display & Video 360 API cost money per request?
No separate per-request fee is charged for ordinary API access. Campaign media and account fees are separate, and current Cloud project requirements should be checked in Google’s documentation.
What is the Display & Video 360 API quota?
Quota limits control how frequently or how much the API can be used. The applicable values depend on the current quota rules and project; check the API’s quota page rather than relying on a number quoted for another project.
Can I increase my API quota?
You can review the quota adjustment process in Google Cloud Console and submit a request where available. Approval is not guaranteed, and the request should explain the workload and why existing limits are insufficient.
Does exceeding quota create an extra bill?
No. Exceeding a usage limit generally causes requests to fail or be throttled; it is not a charge for extra calls. Advertising costs remain separate.
Why do I get an access error even though the API is enabled?
Check that the caller has valid credentials, the right Display & Video 360 account permissions, and access to the specific resource. An enabled API alone does not grant account-level authorization.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.