Hi Chris, If you are authenticating as the client account directly then you only need to specify the developerToken and useragent SOAP headers.
The error is pretty broad, meaning only that there was a problem with OAuth. I would check that you are using the correct scope, and if that still doesn't work feel free to post a sanitized version of the header you are sending. Unfortunately the report download servlet requires a ClientLogin authToken for now, so having only an OAuth access token won't work for now. Unfortunately I don't have any information as to when the servlet will support OAuth. Best, - Eric -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
