Mike: Too much stuff in your header! Take out the emails and
passwords, in V2009+ you use just the auth token for authentication:
<soapenv:Header>
<v20:RequestHeader>
<v20:authToken>xyzzy</v20:authToken>
<v20:developerToken>plough</
v20:developerToken>
<v20:userAgent>V2009 Getall Campaigns</
v20:userAgent>
</v20:RequestHeader>
</soapenv:Header>
Just send the client email/password to the auth service to get the
token, and then use that in the RequestHeader, and you should be good
to go. If you're making lots of API calls for the same client
account, then you'll want to do something like have a daily task that
gets the current auth token and stores it for you to use in the API
calls, otherwise the auth service will start sending back a captcha
challange instead of the token if you call it too often.
Good luck,
-reed
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 [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
