Thanks Eric, I will generate one OAuth token for MCC account.
Yes, It is expires. It may be possible that due to, I am using different oauth token and secret for clients of same mcc account. On Jan 13, 4:00 am, Eric Koleda <eric.kol...@google.com> wrote: > Hi Chirag, > > As far as I know the OAuth 1.0a tokens don't expire naturally. I believe > they only expire if you manually revoke access in the Google Account > dashboard. Are you consistently seeing tokens expire? > > Like the earlier ClientLogin authTokens, you can use OAuth in two ways: > > 1) Authorize using your MCC account, and include a clientCustomerId header > to specify which client account to operate against. > 2) Authorize as the client account directly. > > Option #1 only requires that you have the credentials to the MCC account, > and you only need to generate one OAuth token. Option #2 is more useful > when the clients are not linked to your MCC and the customer doesn't want > to provide you their user name and password. > > Best, > - Eric Koleda, AdWords API Team -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
