CaptchaRequiredError (Ruby API)

瀏覽次數:73 次
跳到第一則未讀訊息

yoshi

未讀,
2012年8月6日 下午3:21:522012/8/6
收件者:adwor...@googlegroups.com

Hi,

Recently I get a lot of CaptchaRequiredError's using the Adwords API. I'm building an application that executes requests to the API frequently
using the Ruby client library. I'm using ClientLogin as authentication method and version v201206 of the API.

All I do is creating an instance of AdwordsApi::Api.new(my_hash_with_settings) and reuse it for every request.

Earlier this hasn't been a problem until now. Even if I dont touch the authtoken endpoint for every request (which I believe I don't) is there still
a request/second limit that also raises the CaptchaRequiredError? By the way, I get the same error in SANDBOX environment.

I don't know how to debug this since I havent' change anything. And I send the same amount of request now as then.

Regards

Hudarsono Hu

未讀,
2012年8月7日 凌晨12:28:012012/8/7
收件者:adwor...@googlegroups.com
HI,

Its the same with me.

You should migrate to OAuth2 as authentication from ClientLogin. Google limit the number of request per minute if we use ClientLogin.

I also still migrating and is experiencing problem with the Ruby Client Library in OAuth2. Hopefully they will answer my email soon.

Cheers

yoshi

未讀,
2012年8月7日 凌晨2:37:362012/8/7
收件者:adwor...@googlegroups.com
Thanks for the answer. I will have a look at Oauth 2.0. But one thing that I'm curious about is, since my application doesn't involve any user input how do I grant
permission with Oauth2 in a convenient way? In my application the requests to the API is handled by a script not a user.

Oliver

未讀,
2012年8月7日 凌晨4:27:382012/8/7
收件者:adwor...@googlegroups.com
I'm just curious to understand why would the type of login affect the quality of service.  Doesn't make sense to me?  Do you have any reference to where Google mentions this?

Oliver

Anash P. Oommen

未讀,
2012年8月7日 晚上11:53:542012/8/7
收件者:adwor...@googlegroups.com
Hi Oliver, Yoshi,

The CaptchaRequiredError is raised by ClientLogin API. ClientLogin API tokens are long lived (typically 2 weeks), so ClientLogin expects that you reuse authTokens instead of generating a new one for every API call. 


Cheers,
Anash P. Oommen,
AdWords API Advisor.

Temla

未讀,
2012年8月8日 凌晨4:42:252012/8/8
收件者:adwor...@googlegroups.com
Hi,

Thanks for the answer. I'm aware about the token lifetime and that we should reuse them. But the code I'm using has been
working for weeks and suddenly it's not working. I have never had a CaptchaRequiredError before and the amount of requests are the same.

So I guess this is probably a something wrong with the the client library (ruby) I'm using or just my own misstake. Anyway, I thought it was strange that
Hudarsono Hu experienced the same behaviour all of a sudden.

Do you know anything about requests per minute?

Regards

Danial Klimkin

未讀,
2012年8月8日 上午11:17:292012/8/8
收件者:adwor...@googlegroups.com
Hello Temla,


There were no changes to the library that could cause this but there may be server-side changes that affected system thresholds.

We don't know exact number of calls allowed before captcha is triggered (and this number can change at any time).


-Danial, AdWords API Team.
回覆所有人
回覆作者
轉寄
0 則新訊息