Deprecation and sunset

With the release of a new version, a deprecated version is given a sunset date, after which that version will no longer be available. Here are some other guidelines to keep in mind:

• We strive to keep at most three major versions available at any one time.
• Major versions have a lifespan of around 12 months—minor versions: 10 months.
• You'll have to perform at most two upgrades per year, and you don't have to upgrade in strict sequential order—for instance, you can upgrade from version (N) directly to version (N+2).
• The overlap between the date when all client libraries are released for the latest version and the version to be sunset is at least 20 weeks.

Our client libraries support any available versions of a service, so you can gradually upgrade by specifying different versions of used services.

Timetable

The following table lists the specific deprecation and sunset dates for each available version, and projected release dates for future versions. We encourage you to upgrade to the latest version as soon as feasible after its release.

API version	Release date	Deprecation date	Sunset date	Upgrade guide
v20	June 4, 2025			Upgrade from v19 to v20
v19.1	April 16, 2025
v19	February 26, 2025			Upgrade from v18 to v19
v18	October 16, 2024	June 2025	August 2025	Upgrade from v17 to v18

View the versions your project is using

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

1. Open the APIs & Services in the Google Cloud Console.
2. Click Google Ads API in the table.
3. On the METRICS subtab, you should see your recent requests plotted on each graph. You can see which methods you've sent requests to in the Methods table. The method name includes a Google Ads API version, a service, and a method name, such as google.ads.googleads.v20.services.GoogleAdsService.Mutate.
4. (Optional) Choose the timeframe you want to view for your requests.

Differences between deprecation and sunset

Term	Deprecation	Sunset
Definition	The deprecated version is a version that is not the latest one. Once a new version is released, all previous versions will be marked deprecated.	The sunset version can no longer be used. Requests sent to this version will fail on or after the sunset date.
Implication	You can still use the deprecated versions until they're sunset, but the references of the deprecated versions are de-highlighted to show that they're not the latest version anymore. We encourage you to upgrade to the latest version as soon as possible to benefit from new features.	You need to upgrade from the sunset versions immediately in order to use the Google Ads API. We highly recommend that you upgrade to the latest version, using the upgrade guide.
Timing	On average, we release a new version every 3 to 4 months, so the given version will be deprecated after approximately 3 to 4 months.	We aim to sunset a version 1 year after its release.
API	API endpoints for the deprecated versions still function as usual. You can access our API endpoints using our client libraries, REST, and so on; however, new features are not added to deprecated versions.	API endpoints for the sunset versions stop working after the sunset dates. The Google Ads API will throw an error if you try to access the API endpoints of the sunset versions.
Client libraries	For purposes of providing compact client libraries, we will stop including deprecated API versions in a new client library version after the deprecation date. This helps you save space when incorporating our client libraries in your projects.	Client libraries no longer support the sunset API versions in any new client library versions after the sunset dates.
Support	We provide regular support for the deprecated versions.	The sunset versions are no longer supported after the sunset date.

Supported client library versions

The table shows which client libraries work with which API versions.

Feature deprecations

Regularly monitor the Google Ads developer blog to be the first to hear about upcoming feature deprecations.

The following table lists the specific feature deprecations that are planned for the Google Ads API. More details for each deprecation can be found in the linked blog posts.

Feature	Description	Effective date	Additional notes
New error messages for invalid developer tokens	Starting on April 28, 2025, an invalid developer token will return DEVELOPER_TOKEN_INVALID for v19.1 and beyond, and DEVELOPER_TOKEN_NOT_APPROVED for versions before v19.1. Invalid developer tokens previously returned OAUTH_TOKEN_HEADER_INVALID, which will still be in use for invalid OAuth headers.	April 28, 2025	This change won't affect anyone who already has working API calls.