Hi Eric, After the account is locked with "Error=CaptchaRequired", as per the docs, we prefix the captcha url with https://www.google.com/accounts and we get the captcha image.
e.g. we use https://www.google.com/accounts/Captcha?ctoken=4MdDSDSmfdkmdsIazxK80fqXrRJX71AYcGebY_ybVwiyfu9MS6qviMskllskdlskdlskoatULEqrug0VX7RFD2qC2-9BJkfs4ebB_xA2e5rXFZQs%3AqdjhsjdVIGVRB-1cuEg (ctoken value changed for privacy reasons) However, after the first captcha url request, all subsequent requests return an image that displays an error message in red text: "Sorry, we are unable to handle your request at this time. Please try again later.". Is this a bug or an intended feature? If a bug, when will this be fixed? If a feature, is there a limitation on the number of times the captcha image is available for manual unlocking? Is our application expected to cache the captcha image bytes or should the above captcha URL work? Assuming that we cache this captcha image and allow the user to re- enter his captcha text in a subsequent session, will his request succeed? This seems like a lot of overkill for application developers and a significant degradation of the end user experience. Please let us know how this should be handled. Thanks On Mar 19, 12:21 pm, AdWords API Advisor <[email protected]> wrote: > Hi, > > I followed up with our authentication team, and they said that if you > wait for about 10 minutes theCAPTCHAchallenges should be resolved on > their own. Let us know if you have any problems. > > Best, > - Eric Koleda, AdWords API Team > > On Mar 18, 5:36 pm, SEM <[email protected]> wrote: > > > Eric: > > > We aren't assuming that 403/CAPTCHAerrors will resolve themselves > > automatically. > > Also, we understand that 403/CAPTCHAerrors could occur for a variety > > of reasons. > > > Our situation is as follows: > > We rolled out a production update to v200909 without ClientLogin / > > authtoken caching resulting in a lot of 403/CAPTCHAlocks for our > > customer base of several hundred customers (due to excessive logins). > > We would prefer not to subject our customers to this inconvenience due > > to this architectural change in authentication and unlock their > > accounts on their behalf. > > That said, if these specific 403/CAPTCHAerrors unlock themselves > > after a period of a few hours (by which time our caching code goes > > in), we can hold off on unlocking these errors manually. > > Could you let us know what the duration is for theseCAPTCHAerrors > > (for this specific reason - i.e. due to throttling restrictions) to > > unlock automatically (if at all)? > > > Thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Have you migrated to v200909 yet? The v13 sunset is on April 22, 2010. 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 To unsubscribe from this group, send email to adwords-api+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
