Google Ads API version 19 will be officially sunset on February 11, 2026. From that date onward, all requests made to v19 will fail, which means any scripts, tools, or integrations still relying on this version will stop functioning. To avoid disruptions, users must migrate to a newer API version before the sunset date.
Although the deadline may seem far away, API migrations often take more time than expected—especially for setups with custom reporting, automated workflows, or multiple dependencies. Treating this as a proactive migration task is strongly recommended.
How to prepare
Google offers support through up-to-date API documentation and release notes, along with clear deprecation guidance between versions.
Developers can also check exactly how v19 is being used by visiting Google Cloud Console and navigating to APIs & Services → Google Ads API → Metrics. This section shows recent API requests, including the API version, service, and method used, making it easier to identify where v19 is still active.
Practical tips
Audit usage early to understand the scope of the migration. Upgrade to the latest API version rather than the minimum required one. Test changes in parallel to avoid unexpected data or logic issues. Check third-party tools to ensure their API timelines align with yours.
Why this matters
An API sunset is not just a technical detail. Broken API access can impact reporting, automation, and decision-making across Google Ads accounts. Planning the migration well ahead of February 11, 2026 helps prevent downtime and ensures long-term stability.