BTW, you don't need to hard code the list of AccountID's, you can use the ManagedCustomerService to retrieve the account tree for an MCC.
On Wednesday, September 19, 2012 8:43:19 AM UTC-4, Alexander Nitschke wrote: > > You can use OAuth 2.0 but it isn't really necessary. Your assumption > regarding OAuth2 with v201206 is wrong as the old login still works. What > doesn't work is the login as a simple client, only logins as MCC will work > with v201206. So you have to login into the MCC, and then change the > ClientID to the one you need (you will have to have a list of AccountIDs > ready for that, but that's true for OAuth2 as well). > > My apologies in advance if there are errors in my text, I'm just trying to > prevent you from doing a lot of unneccary work. > > Best, Alexander > -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords 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
