Hi,
the main (unanswered) question was:
Why do I get a rate limit error _without QuotaErrorDetails_?
IMO that makes automation hard, because it is required by the docs that I
have to wait the provided amount of time. I wouldn't like to resort to
parsing error messages to extract the retry delay.
The linked documentation for the planning service mainly contains details
for the KeywordPlanService while I have problems with the
KeywordPlan_Idea_Service.
Request
-------
MethodName:
google.ads.googleads.v13.services.KeywordPlanIdeaService/GenerateKeywordIdeas
Endpoint: googleads.googleapis.com:443
Headers: {developer-token=REDACTED, login-customer-id=REDACTED,
x-goog-api-client=gl-java/20.0.1 gccl/25.0.0 gapic/25.0.0 gax/2.25.0
grpc/1.54.0 pb/3.21.12}
Body: customer_id: "REDACTED"
keyword_and_url_seed {
url: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
keywords: "REDACTED"
}
keyword_plan_network: GOOGLE_SEARCH
language: "languageConstants/1001"
historical_metrics_options {
year_month_range {
start {
year: 2023
month: MARCH
}
end {
year: 2023
month: MARCH
}
}
include_average_cpc: true
}
Response
--------
Headers:
Metadata(content-type=application/grpc,request-id=SmIXAMeqCnBLAqh1aSFFjw,date=Wed,
03 May 2023 13:06:09 GMT,alt-svc=h3=":443"; ma=2592000,h3-29=":443";
ma=2592000)
Body: null
Failure message: errors {
error_code {
quota_error: RESOURCE_EXHAUSTED
}
message: "Too many requests. Retry in 30 seconds."
}
request_id: "SmIXAMeqCnBLAqh1aSFFjw"
Status: Status{code=RESOURCE_EXHAUSTED, description=Resource has been
exhausted (e.g. check quota)., cause=null}.
Best regards,
Markus
Google Ads API Forum Advisor schrieb am Dienstag, 2. Mai 2023 um 11:05:40
UTC+2:
> Hi Markus,
>
> Thank you for reaching out to us.
>
> Kindly note that due to cost and complexity, the Planning service methods
> listed below are subject to separate limits from other types of requests.
> To see the limitations of this in more detailed, you may check this
> *documentation*.
>
> - *documentation : *
>
> *https://developers.google.com/google-ads/api/docs/best-practices/quotas#planning_services*
>
>
> <https://developers.google.com/google-ads/api/docs/best-practices/quotas#planning_services>
>
>
> Additionally, 1 QPS is calculated as 60 requests per 60 seconds.
> On the other hand, If you are still encountering error after considering
> the information below, then you may provide us with the complete API logs (
> *request* and *response* with *request-id*) generated on your end
> including the error so that our team can further check this and provide you
> with more appropriate recommendations.
>
> - *request* :
>
> *https://developers.google.com/google-ads/api/docs/concepts/field-service#request*
>
>
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#request>
>
> - *response*:
>
> *https://developers.google.com/google-ads/api/docs/concepts/field-service#response*
>
>
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#response>
>
> - *request-id* :
>
> *https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id*
>
>
> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id>
>
>
> Note that logs can be requested or provided to the developer handling the
> Google Ads API transactions when logging of the API requests has been
> enabled. You may check *here* and click your client library for the
> specific guideline to enable it.
>
> - *here: *
>
> *https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging*
>
>
> <https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging>
>
>
> For REST interface requests, you can enable logging via the curl command
> by using the -i flag. This will cause the tool to include the HTTP response
> headers in the output.
>
> You may then send the requested information via the Reply privately to
> author option. If this option is not available, you may send the details
> directly to our [email protected] alias instead.
>
> Best regards,
> [image: Google Logo] Google Ads API Team
>
> ref:_00D1U1174p._5004Q2l8R9Q: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 [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
---
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/4426dedb-bf71-4d72-83ae-2b69329aaf00n%40googlegroups.com.
