Google Ads API v14 will sunset on June 5, 2024. After this date, all v14 API requests will begin to fail. Migrate to a newer version prior to June 5, 2024 to ensure your API access is unaffected.

Here are some resources to help you with the migration:

• Upgrading to the newest version
• Release notes

You can view a list of methods and services your project has recently called using the Google Cloud Console:

1. Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
2. Click on Google Ads API in the table.
3. On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, you’ll see the Methods table, where you can see which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, e.g., google.ads.googleads.v14.services.GoogleAdsService.Mutate. In this way, you can see all versions that you’ve used recently.
4. (Optional) Click on the time frame at the top right of the page if you need to change it.

If you have questions while you’re upgrading, reach out to us on the forum or at googleadsapi-support@google.com.
 - Thanet Knack Praneenararat, Google Ads API Team

Today we’re announcing the deprecation of Structured Data Files (SDF) v5.5. This version will sunset on October 3, 2024.

Migrate to v7, the most recent version, by the sunset date. Instructions on how to migrate to v7 can be found in our migration guide.

Once v5.5 is sunset:

• The default version of partners and advertisers using those versions will be updated to the oldest supported version, v6.
• sdfdownloadtasks.create requests using the sunset version in the request body will return a 400 error.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Starting May 1, 2024, requests to retrieve, create, or run Full Path and Path Attribution reports through the Bid Manager API will return an error. We deprecated both report types in February 2024. We announced this deprecation last November.

After deprecation, running a query using the ReportType FULL_PATH or PATH_ATTRIBUTION generates an empty report. Existing Query and Report resources of these types are still retrievable, and report files generated previously will still be available.

Starting on May 1, 2024, ReportType values FULL_PATH or PATH_ATTRIBUTION and the pathQueryOptions field will sunset. As a result:

• queries.create requests using these values or fields will return an INVALID_ARGUMENT error,
• queries.get, queries.delete, and queries.reports.get requests retrieving resources using these types will return a NOT_FOUND error,
• and queries.list and queries.reports.list responses will not include resources using these types.

We’ve added these details to our change log. To avoid an interruption of service, we recommend that you stop creating, retrieving, or running any reports using these values before the applicable sunset date.

If you have questions regarding these changes, please contact us using our support contact form.

- Trevor Mulchay, Bid Manager API Team

Today we are deprecating Display & Video 360 API v2 and will sunset v2 on September 3, 2024. Migrate to Display & Video 360 API v3 before the sunset date to avoid an interruption of service.

You can read our release notes for more information on updates made to the API in v3, such as the addition of proximity location list management and updates to resource and field names. Follow the steps in our v3 migration guide to help you migrate from v2 to v3.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Google Ads API v13 will sunset on January 31, 2024. After this date, all v13 API requests will begin to fail. Please migrate to a newer version prior to January 31, 2024 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration:

• Upgrading to the newest version
• Release notes

In addition, using the Google Cloud Console, you can view the list of methods and services to which your project recently submitted requests:

1. Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
2. Click on Google Ads API in the table.
3. On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, you’ll see the Methods table, where you can see which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, e.g., google.ads.googleads.v13.services.GoogleAdsService.Mutate. In this way, you can see all versions that you’ve used recently.
4. (Optional) Click on the time frame at the top right of the page if you need to change it.

If you have questions while you’re upgrading, please reach out to us on the forum or at googleadsapi-support@google.com.
 - Thanet Knack Praneenararat, Google Ads API Team

The Content API for Shopping easy onboarding authentication method and tab, which create a service account for you, will not be available in Merchant Center Next. Easy onboarding is still available in Merchant Center Classic.

You can still use existing service accounts that you created using Merchant Center Classic. To set up a service account without using easy onboarding in Merchant Center Classic, follow these steps:

1. Ensure you have an existing cloud project or create a new one in the Google Cloud Console.
2. Generate or access your service account credentials.
3. Download the JSON private key from Google API Console. This JSON private key can be used in the same way as the one downloaded from Merchant Center previously.
4. Add the new service account as a user to your Merchant Center account. If you’re a third-party developer (and don’t have access to the Merchant Center UI for the account), your client will need to complete this step for you.

For more details, see the API documentation.

If you have any questions or concerns, please don't hesitate to contact us via the forum.

Benji Rothman, Content API for Shopping Team

We’re announcing our tentative 2024 release and sunset schedule for upcoming versions of the Google Ads API to bring greater clarity to your planning cycle. Please keep in mind that these dates are only estimates and may be adjusted going forward. Additionally, releases may be added, removed, or switched between major and minor versions.

Version	Planned Release Type*	Projected launch*	Projected sunset*
V16	Major	January/February 2024	January 2025
V16.1	Minor	April/May 2024	January 2025
V17	Major	May/June 2024	May 2025
V17.1	Minor	July/August 2024	May 2025
V18	Major	September/October 2024	September 2025

*Estimated and subject to change

Where can I learn more?

• Release Notes
• Deprecation Schedule

Check back for any updates as the blog is the best place to stay informed about developments in this space.

If you have any questions or need additional help, contact us via the forum.
- David Stevens, Google Ads API Product Manager

Buy on Google for Search and Shopping will no longer be available starting September 26, 2023. All Merchant and Consumer support will end for Buy on Google on Search on November 25, 2023. The only exception is that the orders.get and orders.list methods will remain available for Search and Shopping until October 30, 2024, so that merchants can download their historical order data.

See below for the specific timeline of when Buy on Google methods will no longer be available for the Search and Shopping program.

June 28, 2023 onwards:

• buyongoogleprograms.requestreview
• buyongoogleprograms.onboard
• buyongoogleprograms.activate
• buyongoogleprograms.pause

September 30, 2023:

• buyongoogleprograms.get
• buyongoogleprograms.patch

October 31, 2023:

All the orders related resources (orders, orderinvoices, orderreports, orderreturns, ordertrackingsignals) and all their underlying methods. The only exception is that the orders.get and orders.list methods will remain available for Search and Shopping until October 30, 2024, so that merchants can download their historical order data.

If you are currently using the Buy on Google endpoints for Search and Shopping via the Content API, you will need to stop using these services for Search and Shopping before the dates listed above, as your requests will start to fail after that date.

If you have any questions or concerns, please don't hesitate to contact us via the forum.

Benji Rothman, Content API for Shopping Team

Google Ads API v12 will sunset on September 27, 2023. After this date, all v12 API requests will begin to fail. Please migrate to a newer version before September 27, 2023 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration:

• Upgrading to the newest version
• Release notes

In addition, using the Google Cloud Console, you can view the list of methods and services to which your project recently submitted requests:

1. Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
2. Click on Google Ads API in the table.
3. On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, you’ll see the Methods table, where you can see which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, e.g., google.ads.googleads.v12.services.GoogleAdsService.Mutate. In this way, you can see all versions that you’ve used recently.
4. (Optional) Click on the time frame at the top right of the page if you need to change it.

If you have questions while you’re upgrading, please reach out to us on the forum or through googleadsapi-support@google.com.
 - Thanet Knack Praneenararat, Google Ads API Team

Today we’re announcing the deprecation of Structured Data Files (SDF) v5.4. This version will be fully sunset on February 27, 2024.

Please migrate to v6, the most recent version, by the sunset date. Once v5.4 is sunset::

• The default version of partners and advertisers using those versions will be updated to the oldest supported version, v5.5.
• sdfdownloadtasks.create requests declaring the sunset versions in the request body will return a 400 error.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

As announced in March 2023, Display & Video 360 (DV360) API v1 will sunset on September 14, 2023. Please migrate to DV360 API v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about v2. Follow the steps in our v2 migration guide to help you migrate from v1 to v2.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

In August 2023, the Google Ad Manager SOAP API Client Library for PHP will start requiring PHP version 8.0 or higher. The version of the client library that adds support for Google Ad Manager API v202305 will be the last version that supports PHP 7. We’ll still fix security issues for this client library version until Google Ad Manager API v202305 is sunset, but no new features will be added.

All PHP 7 versions reached their end of life in 2022. The PHP development team no longer provides security fixes for these versions, so we highly recommend migrating to newer versions as soon as possible.

Here are useful resources to help with the PHP migration:

• The PHP support version calendar
• How to migrate from PHP 7.4.x to PHP 8.0.x

If you have any questions regarding this change, feel free to comment directly on the GitHub issue.

Pierrick Voulet, Google Ads API Team

On Wednesday, May 31, 2023, in accordance with the deprecation schedule, v202205 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

Additionally, support for Ad Manager API v202202 is being extended until the same date, May 31, 2023. We've heard from a number of users that they need additional time to complete the Ad Exchange Historical report migration. Note that v202202 is the last version with support for Ad Exchange Historical reports.

When you’re ready to upgrade, check the full release notes to identify any breaking changes. Here are a few examples of changes that may impact your applications:

• v202211
  • Replaced the string field thirdPartyImpressionTrackingUrl with the list field thirdPartyImpressionTrackingUrls for multiple creative types including ImageCreative. Currently only a single URL may be provided in the list.
  • Removed support for OPTIMIZATION reporting columns.

As always, feel free to contact us on the developer forum with any questions.

- Chris Seeley, Ad Manager API Team

In the Content API for Shopping, we informed you last June that new Merchant IDs were migrating from 32 bit to 64-bit signed integers.

Existing Merchant IDs haven’t changed. Beginning on March 13, 2023 new Merchant IDs created could be in the 64-bit signed range. Through a slow rollout over the next few months, a higher percentage of new Merchant IDs will be in the 64-bit signed range. By June 2023, all new Merchant IDs created will be in the 64-bit signed range.

To avoid any issues, please make sure your applications are fully compliant with IDs within a range of 64-bit signed integer values.

If you have any questions or concerns, please don't hesitate to contact us via the forum.
Benji Rothman, Content API for Shopping Team

Starting on April 24, 2023, the Content API for Shopping methods productstatuses.list and productstatuses.get will include issues from all eligible destinations by default. This will likely increase the size of the response you get back from the same call.

Currently, the responses you get when using the productstatuses.list and productstatuses.get methods only include issues from Shopping Ads and don’t include issues from other destinations, for example free listings issues.

Including issues from all eligible destinations will let you provide your users with an overall better experience. This change will improve your issue visibility across all destinations. In turn, you will see an increase in the number of results, or the size of responses you’ll receive.

No action is needed from you as the free listing issues will now be included by default when using the Content API for Shopping methods productstatuses.list and productstatuses.get.

However, if you want to keep the calls to only display issues from Shopping Ads, we suggest setting the query parameter destinations[] in the productstatuses methods to Shopping.

Learn more about the changes to the product statuses methods in the Content API for Shopping Product statuses documentation.

If you have any questions or concerns, please don't hesitate to contact us via the forum.
Benji Rothman, Content API for Shopping Team

Today we are deprecating Display & Video 360 API v1. While deprecated, v1 will no longer be updated. We will sunset v1 on September 14, 2023. Migrate to v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about new features available in v2, such as the ability to retrieve YouTube & Partners line items, ad groups, and ads. Follow the steps in our v2 migration guide to help you migrate from v1 to v2.

After supporting and regularly updating Display & Video 360 API v1 for over three years, we are excited to introduce new Display & Video 360 API features using a more consistent version release and sunset schedule. A projected schedule will be announced on this blog at a later date.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

The Ad Exchange Buyer II API is now deprecated, and the following resources will be sunset on September 29th, 2023:

• accounts.clients
• accounts.clients.invitations
• accounts.clients.users
• accounts.creatives
• accounts.creatives.dealAssociations
• accounts.finalizedProposals
• accounts.products
• accounts.proposals
• accounts.publisherProfiles

Accessing the sunset resources will return an error response following the sunset date. Note that RTB Troubleshooting resources aren’t included in this list, and will continue to be supported until further notice.

To continue programmatically accessing your Client Access and Marketplace configurations, you should migrate to the Authorized Buyers Marketplace API. For more information, we recommend that you review the Marketplace guide and samples. If you have any questions or feedback, feel free to reach out to us via the Authorized Buyers API Forum.

- Mark Saniscalchi, Authorized Buyers Developer Relations

In July 2023, the Google Ads API client library for PHP will start requiring PHP version 8.0 or higher. The version of the client library that adds support for the Google Ads API v14 will be the last version that supports PHP 7. We’ll still fix security issues for this client library version until the Google Ads API v14 is sunset, but no new features will be added.

All PHP 7 versions reached their end of life in 2022. The PHP development team no longer provides security fixes for these versions, so we highly recommend migrating to newer versions as soon as possible.

Here are useful resources to help with the PHP migration:

• The PHP support version calendar
• How to migrate from PHP 7.4.x to PHP 8.0.x

If you have any questions regarding this change, feel free to comment directly on the GitHub issue.
 - Thanet Knack Praneenararat, Google Ads API Team

Google Ads API v11 will sunset on March 29, 2023. After this date, all v11 API requests will begin to fail. Please migrate to a newer version prior to March 29, 2023 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration:

• Upgrading to the newest version
• Release notes

In addition, using the Google Cloud Console, you can view the list of methods and services to which your project recently submitted requests:

1. Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
2. Click on Google Ads API in the table.
3. On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, you’ll see the Methods table, where you can see which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, e.g., google.ads.googleads.v11.services.GoogleAdsService.Mutate. In this way, you can see all versions that you’ve used recently.
4. (Optional) Click on the time frame at the top right of the page if you need to change it.

If you have questions while you’re upgrading, please reach out to us on the forum or at googleadsapi-support@google.com.
 - Thanet Knack Praneenararat, Google Ads API Team

The Bid Manager API v1.1 will sunset on April 27, 2023. The Bid Manager API v1.1 was deprecated in August 2022 and originally scheduled to sunset on February 28, 2023.

Please migrate to v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about v2. Follow the steps in our v2 migration guide to help you migrate from v1.1 to v2.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team