Developer over Qps - lockout period?
devin
some testing - because now I'm getting a "Developer Over Qps" message
on simple calls like http://openapi.etsy.com/v2/private/users/__SELF__.
Is there a lockout period after we go over this limit?
In addiiton, I'm not seeing any information about these errors on the
Mashery dashboard. Shouldn't we see something there too?
Aaron Gardner
I confirmed with Mashery that there is no "lockout period" after an
API key exceeds its QPS (queries per second) throttle limit. In other
words, the throttle should reset the next second.
Are you still getting "Developer Over Qps" error messages when you
make calls now?
We have Mashery investigating if your key (or any others) had an issue
with "Developer Over Qps" errors yesterday.
Can you confirm you only saw this issue with your v2 key for the
Metricly application (I assume this is the case given the URL you
provided).
Is it possible your v2 key exceeded its daily API call quota at some
point yesterday in addition to its QPS limit?
The daily quota information is available in the Mashery dashboard
here: Keys > Etsy API v2 > View Report > Current Quota Usage
Unfortunately the QPS throttle information is not directly available
in the Mashery dashboard.
Thanks,
Aaron Gardner
Developer API Team
Etsy.com
agar...@etsy.com
Justin Kerr Sheckler
I have the default rate limits for /v2/private set at 5/sec,
10,000/day. These limits apply to oauth access tokens, or in other
words, the rate limits are unique to each signed-in user using
Metricly.
Unfortunately, Mashery doesn't (yet) provide us with a way to increase
the limits on a per-app basis. They're working on fixing this hole in
their infrastructure. Please bear with us on that point.
Let me know what calls you're making and how frequently, and maybe we
can find a way to either decrease your call volume, or change the
OAuth default limits.
JKS
--
Justin Kerr Sheckler
Developer API Lead
Etsy.com
jus...@etsy.com
devin
We appear to have things working again. Our best guess is that there
was a new error coming from the API - because we were asking for
fields that weren't yet supported (this didn't used to throw an error)
- and not recognizing that error was causing some retries on our end
that may have pushed us over the 5 qps limit. We were not over the
queries per day limit though.
-Devin
> > On Tue, Jul 20, 2010 at 3:30 PM, devin <de...@metricly.com> wrote:
> >> I'm guessing we ran a query that pushed us over the QPS limit during
> >> some testing - because now I'm getting a "Developer Over Qps" message