We recently encountered a critical issue related to API deprecation. One of the reporting endpoints we depend on began returning all-zero spend data without any prior indication of deprecation. Since the report was successfully returned (but with zeros), our system interpreted it as valid and assumed the remaining daily budget was 0.
We only noticed after the API had already stopped returning usable data.
Questions:
Is there a way to proactively detect pending or recent API deprecations that affect reporting endpoints?
Are there any webhook notifications, changelog subscriptions, or version deprecation calendars that can be integrated into our monitoring systems?
Are "zeroed" reports a known symptom of deprecation for specific services?
Any guidance on recommended practices to detect/report such issues earlier would be very helpful.

Hi,
Thank you for reaching out to the Google Ads API support team.
Please find answers to your queries:
I suggest you follow our Blog Post and Release Notes to get information on the latest version releases and changes that happen in the Google Ads API. You can also follow our Deprecation and sunset guide.
I would like to inform you that you will receive notification about the version deprecation when your developer token was used to make requests to the Google Ads API. Also, another way is to follow our Blog Post and Release Notes to get information on the latest version releases and changes that happen in the Google Ads API.
Regarding the Zeroed reports, when you execute a query, you may encounter metrics for entities that are zero. This could be because:
I would recommend you refer to the Zero metrics for more information.
If you still need further assistance on this, please provide Customer ID of your Google Ads account.
Additionally, provide us with the complete API logs (request and response logs with request-id and request header) generated at your end, so that we can investigate this issue further on our end and assist you accordingly.
If you are using a client library and haven't enabled logging yet, I would request that you enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.
You can send the details via Reply privately to the author option, or direct private reply to this email.
![]() |
Google Ads API Team |
[2025-07-02 04:35:34Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rgxe7:ref" (ADR-00316701)