Hi Justin, 

It looks like you are taking about the report rate limit error 
specifically. The recommended approach since you are having basic access 
would be to ensure that within any given 24-hour period, your application 
is not issuing more that 1000 report requests. Having this kind of a logic 
will ensure that your application does not encounter rate limit errors at 
the first place. If you encounter a report rate limit error, you can catch 
that and retry only after the specified waiting time. This will make sure 
that you are not making any additional calls during the wait time. If your 
application needs to make more than 1000 report calls a day, you could 
consider upgrading your access to Standard Access 
<https://developers.google.com/adwords/api/docs/guides/rate-limits#operational_limit_based_on_access_level>
. 

Hope this answers your question. 

Thanks,
Sreelakshmi, AdWords API Team

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
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/47951f7d-45d2-4f9a-9515-e820841bd8c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • API Rate... Justin Coon
    • Re:... 'Sreelakshmi Sasidharan (AdWords API Team)' via AdWords API Forum
    • Re:... Justin Coon
    • Re:... Justin Coon

Reply via email to