Hi Eric, This is not an MCC situation, which is why switching to OAuth makes sense. We don't have have UI or API access to the customer's Adwords account. Instead, we are having them grant us an access token. So in this scenario, what information needs to be in the SOAP header?
Is the AuthenticationError.OAUTH_TOKEN_HEADER_INVALID likely caused by a mismatch in the above? Or does it mean there is a problem with how I've formatted the URL? Would it help if I showed what the URL looks like? But perhaps I should have first asked if this is going to work. If I setup a report using OAuth, can I download the report using the non-oauth client library? If not, I guess we'll have to wait until the download supports OAuth. When do you think the download servlet will be updated to look for the oauth parameters? Thanks for all your assistance. Chris -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
