Hi,

The limits are normally associated to mutate operations only of the AdWords 
API.

If you have further clarifications about Rate Limits, you may open a new 
thread regarding your concern.

Regards,
Dannison
AdWords API Team

On Wednesday, August 8, 2018 at 4:22:14 AM UTC+8, Константин Латыпов wrote:
>
> Tell me please Is this limits only for mutate operations or for read 
> requests too?
>
> Best regads
>
> вторник, 20 августа 2013 г., 18:33:06 UTC+4 пользователь Jeremy Aube 
> написал:
>>
>> You should add code that handles any RateExceededError that you get. 
>> Generally the error will include information about how long you should back 
>> off for (usually 30 seconds). It may take a full minute though before you 
>> can make a successful request, however, so you should be prepared to catch 
>> the error at least twice in a row.
>>
>> On Monday, August 19, 2013 7:29:01 AM UTC-4, Omri Cohen wrote:
>>>
>>> Thanks Jason!
>>> Are you suggesting trial and error as the best practice to learn about 
>>> my limits?
>>>
>>> On Monday, August 19, 2013 2:11:54 PM UTC +3, Jason Stedman wrote:
>>>>
>>>> Omri, 
>>>>
>>>> The System Limits documentation is located here:
>>>>
>>>> https://developers.google.com/ adwords / api / docs / appendix / Limits 
>>>> <https://developers.google.com/adwords/api/docs/appendix/limits>
>>>>
>>>> You will not see any kind of rate limits there as the AdWords API rate 
>>>> limits are dynamic. It is expected that all clients properly back off 
>>>> if the current rate limit is exceeded. A RateExceededError is thrown 
>>>> if a client exceeds the rate limit.
>>>>
>>>> Hope this answers your question.
>>>>
>>>> Jason
>>>>
>>>>
>>>>
>>> This e-mail, as well as any attached document, may contain material 
>>> which is confidential and privileged and may include trademark, copyright 
>>> and other intellectual property rights that are proprietary to Kenshoo Ltd, 
>>> its subsidiaries or affiliates ("Kenshoo"). This e-mail and its 
>>> attachments may be read, copied and used only by the addressee for the 
>>> purpose (s) for which it was disclosed herein. If you have received it 
>>> in error, please destroy the message and any attachment, and contact us 
>>> immediately. If you are not the intended recipient, be aware that any 
>>> review, reliance, disclosure, copying, distribution or use of the contents 
>>> of this message without Kenshoo's express permission is strictly prohibited.
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/f6e15486-30a6-4981-bed5-8288ecbd2c03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • ... Константин Латыпов
    • ... 'Dannison Yao (AdWords API Team)' via AdWords API and Google Ads API Forum

Reply via email to