Though on lib. v21.0.0 and all known code using API v17, getting occasional random blocking errors about "v15 is deprecated".
This is only happening on about 9% of requests within the same loop for which the cloud console shows v17 is being primarily used. I will make about 90 of the same calls, and 83 of them will work, but 7 or 8 will give this error.
Is this a bug, or if not - how may I know what I may have missed?
I have also submitted this as an issue in the Google Ads .NET Github issue tracker.
Error shown below:
Bad Request | [{
"error": {
"code": 400,
"message": "Request contains an invalid argument.",
"status": "INVALID_ARGUMENT",
"details": [
{
"@type": "type.googleapis.com/google.ads.googleads.v15.errors.GoogleAdsFailure",
"errors": [
{
"errorCode": {
"requestError": "UNSUPPORTED_VERSION"
},
"message": "Version v15 is deprecated. Requests to this version will be blocked."
}
],
"requestId": "gPbhZUjQgKfdCbAer-ZQGQ"
}
]
}
}
]
Hi,
Thank you for reaching out to the Google Ads API support team.
Double-check your code and ensure all API calls are explicitly made using the v17 endpoints and methods. Remove any leftover code that might be still using v15.
However, to do further checks, kindly provide the complete API logs (request and response logs with request-id and request header) generated at your end when API calls triggers so that we can check request and response data completely and get back to you.
If you are using a client library and haven't enabled the logging yet, I would request that you enable logging for the specific client library that you are using. You can refer to the guides .Net 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 |