Our application and I am sure a lot of other peoples applications do a lot of api calls in the background.
This is how things work with V13. The email, password, token etc.. are stored in a db and the application uses that to communicate with the API. One of the codes that the 2009 ClientLogin API returns is a CAPTCHA. We have a few hundred accounts being processed in the background daily and we cannot expect the user to be around when an operation takes place. The browser is not even around. All the execution happens in a linux box. We have no way of alerting the user to a CAPTCHA challenge. I would really appreciate it if you could provide some details of this CAPTCHA challenge. Essentially, what will cause this challenge to be raised? Is there any frequency associated with it i.e you raise it every few months or so? Can we indicate to the API to just return an BadAuthentication code instead or a captcha challenge? Supposing I store the Auth Token and after a week when I try to call the CampaignService api using this token it fails. I would then make a ClientLogin request and try to get a new authtoken. Will this cause a CAPTCHA challenge? Again it would be great if we can indicate to the API not to raise the CAPTCHA challenge. It doesn't really integrate very well with applications that run in the background. -- 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=.
