Hi, I experienced some differences in the authentication between AdWords and Google Ads API access using the Java libs.
We have a setup with 1) The main MCC account that gets authenticated. 2) Below that a MCC which we use as "clientCustomerId" / "login-customer-id". 3) Below that a "normal" account. This setup works fine with the AdWords API. When using this with the Google As API e.g. to access the sitelinks of the account, a USER_PERMISSION_DENIED error is raised. In other kinds of setups, our Google Ads API access works fine though. So our code seems to be correct. Is the "login-customer-id" required to be the authenticated main MCC account instead? Why is there a difference in the behavior between AdWords and Google Ads API? I apologize if this has already been answered elsewhere. But I was able to find a definitive answer to that in the other posts. Regards, Markus -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/db0e867e-4ec0-49bc-baf3-acde8baa173cn%40googlegroups.com.
