Migrate from Display & Video 360 API v4 to v5

Last update: 2026-10-22

Migrate your application

Migrating from v4 to v5 requires updating your endpoint URLs to call v5, updating your application to account for breaking changes, and reviewing any new features that may benefit your integration.

Update your API calls from v4 to v5

To use v5 instead of v4, you need to update your requests to use new v5 endpoints.

For example, to call the advertisers.get method with v4, use the following URL:

GET https://displayvideo.googleapis.com/v4/advertisers/advertiserId

For v5, update the URL to the following:

GET https://displayvideo.googleapis.com/v5/advertisers/advertiserId

If you are using a client library to make requests to the API, use the most recent version of the client library and update your configuration to use v5.

Make required changes

Display & Video 360 API v5 introduces a number of breaking changes. Review the following instructions and make the required changes relevant to your existing use of the Display & Video 360 API.

For an exhaustive list of the differences between Display & Video 360 API v4 and v5, see the release notes.

Update inventory source retrieval and targeting to use new IDs and types

Display & Video 360 API v5 changes how inventory source deals and auction packages are retrieved and targeted.

In v4, InventorySource resources retrieved using the inventorySources service represent both inventory source deals and auction packages. Both deals and auction packages are targeted using TARGETING_TYPE_INVENTORY_SOURCE.

In v5, inventory source deals and auction packages are handled separately:

This update changes the IDs used for existing deals and auction packages, so you can't use any previously cached InventorySource resource IDs after migration.

In addition to these changes, v5 also removes the ability to create, update, and edit accessors of inventory sources.

Update audience targeting logic for Demand Gen and YouTube resources

Display & Video 360 API v5 updates audience targeting logic for Demand Gen and YouTube resources to use individual assigned options for each targeted audience list.

In v4, all audience targeting is managed using TARGETING_TYPE_AUDIENCE_GROUP.

In v5, audience targeting assigned to Demand Gen and YouTube ad groups is managed using one of the following targeting types and AssignedTargetingOption resource fields, depending on the type of audience:

Line items will continue to use a single TARGETING_TYPE_AUDIENCE_GROUP AssignedTargetingOption to manage audience targeting for all types.

Upgrade to the Data Manager API for Customer Match audience management

Display & Video 360 API v5 removes the ability to create and manage the membership of Customer Match audiences by removing the following methods:

  • firstPartyAndPartnerAudiences.create
  • firstPartyAndPartnerAudiences.editCustomerMatchMembers
  • firstPartyAndPartnerAudiences.patch

To continue managing Customer Match audiences, upgrade your workflows to use the Data Manager API.

Add support for retrieving Digital Out of Home insertion orders

Display & Video 360 API v5 adds support for retrieving Digital Out of Home insertion orders.

If your advertisers use Digital Out of Home advertising, upgrade any integration calling advertisers.insertionOrders.list in anticipation of the inclusion of InsertionOrder resources with insertionOrderType field value of OUT_OF_HOME.

In v5, line items under Digital Out of Home insertion orders will continue to be retrievable as they were in v4.

Update references to Adloox to Peer39

In v5, fields and enum values referencing Display & Video 360 third-party brand suitability integration with Adloox (also referred to as Scope3) have been updated to Peer39:

Update fields for YouTube line items, ad groups, and ads

In v5, various fields in LineItem, AdGroup, and AdGroupAd resources have been removed or updated. Update your resource retrieval logic to account for these changes.

In the LineItem resource:

In the LineItem and AdGroup resources:

In the AdGroupAd resource:

Remove references to deprecated enum values

In v5, previously deprecated enum values have been fully removed. While use of these values in requests to the API would result in an error in v4, this change removes any reference to them from v5 client libraries. Any references to these deprecated values in your code may cause errors when upgrading to v5.

Enum types that have impacted values include ContentRatingTier, GoogleAudienceType, SdfVersion, and SensitiveCategory. See our release notes for an exhaustive list of all removed enum values.

Review new features

In addition to the breaking changes, v5 also introduces the following new features: