Hi Teja I think I know where the problem is. When I created the test MCC (897-646-0211) I connected it to my existing email address which I use for production accounts. The reason I did so is because the form <https://adwords.google.com/um/Welcome/Home?testAccount=true&sf=mt&pli=1#ta> to create test MCCs allows to link an existing account in the bottom yellow box (and who wants to open an extra new account if using an existing one is possible too?). So, even though my test MCC is clearly marked as "test account" in the top right, I think all the regular accounts I created below the test MCC were *not *created as test but production accounts. If that *is* the reason of the problem, then your account creation logic is not as stated in the help manuals, where you describe that each account created under a test MCC is a test account.
I then created another, new email address, created a test MCC for that email address and then created test accounts under that new test MCC. Suddenly my API requests to that new test account structure started to work fine. My case would prove that this depends on the email address with which one is logged in. So, in my opinion this is wrong and should be fixed. If the categorization of a new accounts beneath a test MCC is not determined by the parent test MCC, but by the user who is logged in, and if this is the intended behaviour, then you should update the help manuals to reflect this logic. Otherwise, if the categorization of a new accounts beneath a test MCC should not be determined by the logged in user and just by the parent test MCC, then you should fix that in your systems. Regards Aleksandar On Thursday, September 27, 2018 at 10:29:25 PM UTC+2, Teja Makani wrote: > > Hello Aleksandar, > > The DEVELOPER_TOKEN_NOT_APPROVED > <https://developers.google.com/adwords/api/docs/reference/v201809/AdGroupAdService.QuotaCheckError.Reason> > error > occurs when you are trying to access a production account with the > developer token having test access. Could you please confirm whether the > clientCustomerId mentioned in the request headers containing the test > account? If you are sure that your are targeting to the test account and > still facing the issues, please share the complete SOAP logs(request and > response) without redacting any information. You could use reply privately > to the author option while sharing. > > Regards, > Sai Teja, AdWords API Team. > > On Thursday, September 27, 2018 at 3:10:47 PM UTC-4, Aleksandar wrote: >> >> Hi >> >> I created a test MCC (897-646-0211) and then created a test account >> (890-811-6327) under the test MCC. But, I'm always getting >> the QuotaCheckError.DEVELOPER_TOKEN_NOT_APPROVED error when I query the >> test account 890-811-6327. >> >> Aren't all accounts under a test MCC supposed to be test accounts where I >> can use an unapproved developer token? >> >> I can send the SOAP request / error log if you need it. >> >> Thanks >> Aleksandar >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/bbb0e1a8-513d-4fb1-9a5d-3bd3fb6115bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
