Hi Peter and Sohail, Thank you for your reply.
Kindly note that the API request and API operations are different from each other. A mutate request can have 10,000 operations per request. As said by Sohail, you are using a simple keyword idea search request. This request is the planning services in the Google Ads API. Due to cost and complexity, the Planning service methods listed below are subject to separate limits from other types of requests. Limited to 1 request per second per CID or developer token: KeywordPlanService.GetKeywordPlan KeywordPlanService.GenerateHistoricalMetrics KeywordPlanService.GenerateForecastMetrics Requests that violate these limitations are rejected with the error: RESOURCE_EXHAUSTED. 1 QPS is calculated as 60 requests per 60 seconds. All requests to Keyword Planning services for both standard and basic access are rate limited. Fewer requests are allowed per minute when compared to other services. Our recommendation is to cache or store results as you will receive the same response over a long time span. For example, if you request a set of existing keywords, the response is not going to change over a period of hours or days. In the case of historical metrics, the statistics refresh monthly. Moreover, I would recommend setting up short delays between requests or combine more operations in fewer requests. The server throws this error once it detects that your request has exceeded the system frequency limit. When you retry requests, you may continue using an exponential backoff policy by delaying 5-10 seconds. For example, if you first pause 5 seconds before the first retry, you could pause 10 seconds after the second and 20 seconds after the third retry. Exponential backoff helps ensure you are not calling the API too aggressively. In addition, we suggest setting a reasonable upper bound for the total number of concurrent tasks that are going to make requests (across all processes and machines), and adjusting upward to optimize your throughput without exceeding the rate limit is recommended. Otherwise, you may possibly experience the exceeding rate limits that the client app is spawning an excessive number of parallel tasks since we don't limit the number of parallel requests a client app can have, this can easily exceed the Requests Per Second limit at the developer token level. However, Throttles can be implemented at the consumer side by limiting the number of concurrent consumers, or implement rate limiters or throttlers for either the producers or consumers.For more information, you may refer to this throttling QPS from the client side (check out Throttling and rate limiters). Let us know if you need further clarification. Regards, Yasar Google Ads API Team ref:_00D1U1174p._5004Q2giL6I:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/CB1oA000000000000000000000000000000000000000000000RMH1QE00AYlaQ-LDR0ygIpk-Qu0JIg%40sfdc.net.
