Hi, The refresh token gives you the same access rights as the user who accepted the OAuth request, so if you were logged in as the main MCC when you accepted the OAuth request then you should be able to use the refresh token for API calls against any of its child accounts.
Our OAuth 2.0 Migration for a Single Top Level MCC guide<https://developers.google.com/adwords/api/docs/guides/clientlogin-to-oauth2-single-mcc> may be useful for you. Even if you aren't in the process of migrating off of ClientLogin, the guide contains details on how to use a top level MCC to access child accounts. Cheers, Josh, AdWords API Team On Tuesday, April 1, 2014 8:51:04 AM UTC-4, Gabachao wrote: > > Hello, > > We have a main MCC that grants us access to other "sub"-MCCs. > > Do we need a specific Refresh Token for each "sub"-MCC or can we use the > Refresh Token of the main MCC? > > Thanks in advance > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] 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 Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
