Hi,
Pete's answer is spot-on. You can reuse an AuthToken by caching it using
Pete's suggestion and then using the setAuthToken setter on the AdWordsUser
to tell it to reuse the existing AuthToken. The library first checks that
it has an authToken before generating a new one. Here's the sett
Daniel,
You definitely want to be caching your Auth Tokens. Using Java, you
can stick them in a static map with a key of clientId. The
documentation says they're good for ~2 weeks, but I only cache them
for 5 days as I've run into problems before with longer expirations.
As far as testing whethe
Hi Kevin,
>Could you provide a little more detail about the exact error you are receiving?
sure, but i don't know what more i can say ...
I work with the Java Client Library. Every night, i want to download a
Keyword Performance Report for several Accounts.
While doing this, i sometimes get the
Hi Daniel,
Could you provide a little more detail about the exact error you are
receiving?
It sounds like the script requests a new Client Login token each time it
runs. These authtokens are valid for 2 weeks. Have you tried caching them
and see if reusing them prevents this type of problem
Hi,
since a few weeks, we have massive problems with the Adwords API...
When i try to generate a report, i (sometimes) get the following
error:
javax.xml.rpc.ServiceException: Could not get Client Login token for
user: Auth token could not be retrieved because of IOException: www.google.com
Usu
