When doing sandbox tests yesterday I learned that calling the google clientlogin with a too high frequency gives a temporary permission denied.
Our platform is highly distributed and I would rather not have the individual sync processes dealing with authentication token issues. My preferred solution would be to have a central process that can update the authtoken on a regular basis, not having to wait for the token to expire. Is there anyway to force a token to expire? Also, are the requests per second limitations limited to the authentication token or limited to the individual client accounts in the MCCs. Thanks -- 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.
