API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-178 · Enforcement & amendments

Google Ads API v21 sunsets and requests begin failing

Google Ads API v21 reached sunset on 5 August 2026; from that date all v21 API requests begin to fail, while integrations can move to a newer supported version.

Google Ads APIv21API versionsunsetenforcement

Previous state

Before the sunset boundary, integrations could continue sending requests to Google Ads API v21 while planning migration to a newer API version.

Current state

From 5 August 2026, Google Ads API v21 is sunset and v21 requests begin to fail; callers must use a newer supported API version for continued access.

Who needs to care

Developers, automation and integrations that still send requests to Google Ads API v21.

What to do

Identify any remaining v21 request paths, migrate them to a newer supported Google Ads API version, and verify production traffic no longer depends on v21.

What the source does not prove

Google's notice applies specifically to Google Ads API v21. It does not retire Google Ads API as a product, and later supported API versions remain outside this event.

Lifecycle history

Dated event sequence

  1. v21 sunset reminder published

    Google published the version-specific reminder directing v21 callers to migrate to a newer version before the enforcement date.

  2. v21 sunsets

    Google states that all v21 API requests begin to fail from this date.

Evidence ledger

First-party sources

  1. 01
    Google Ads Developer Blog — Google Ads API v21 sunset reminder

    Official Google Ads API version-sunset and enforcement notice · 2026-06-25

    Open official source ↗