Timeline for Why do I get a throttle violation after 300 requests while using a key but no access_token?
Current License: CC BY-SA 3.0
26 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2014 at 22:19 | comment | added | Dennis Williamson | I had a problem similar to this and it was caused by one query (which I only run once) which was missing the key. Running keyed queries more than 300 times causes an unkeyed query to fail for throttle violation. Fixing the missing key fixed the problem. | |
| Jan 9, 2012 at 20:42 | vote | accept | agent86 | ||
| Jan 9, 2012 at 19:08 | history | edited | agent86 | CC BY-SA 3.0 |
added 110 characters in body
|
| Jan 9, 2012 at 18:39 | history | edited | Kevin Montrose |
edited tags
|
|
| Jan 9, 2012 at 18:39 | answer | added | Kevin Montrose | timeline score: 1 | |
| Jan 8, 2012 at 22:24 | comment | added | patridge |
Not that it helps, but I ran into the same issue on polling the API, even with ?key={my_key} in all the request. Fortunately, I could just switch from my home IP to a different one by running my machine's traffic through my phone (not ideal for speed, but it bought me enough time to call it a day and wait for the reset).
|
|
| Jan 8, 2012 at 19:18 | history | edited | agent86 | CC BY-SA 3.0 |
edited title
|
| Jan 8, 2012 at 18:07 | comment | added | agent86 | @Jonathan. - there's no web component to the tool whatsoever, and the URLs in the key were all bogus, so I had to set one up in order to get an access_token. I ran the test with the token and edited the question to show the results. | |
| Jan 8, 2012 at 18:06 | history | edited | agent86 | CC BY-SA 3.0 |
added 245 characters in body
|
| Jan 7, 2012 at 23:05 | comment | added | Jonathan. | From your update, it seems to definitely be a bug. But you can just get an access_token using your browser the url and query parameters are in the documentation, then just copy the access_token and put it in the url your app uses. Actually it might help a bit, because if the access_token and app key don't match it will send back a different error. | |
| Jan 7, 2012 at 19:35 | comment | added | agent86 | @Jonathan., I don't have a flow for that in my app currently. I'll see what I can do. | |
| Jan 7, 2012 at 19:25 | comment | added | Jonathan. | Try adding an access token, it should help narrow things down (more information the better) when Kevin see this. | |
| Jan 7, 2012 at 17:33 | history | edited | agent86 | CC BY-SA 3.0 |
added 877 characters in body; edited tags; edited title
|
| Jan 6, 2012 at 19:36 | history | edited | agent86 | CC BY-SA 3.0 |
added 257 characters in body
|
| Jan 6, 2012 at 18:51 | history | edited | Jonathan. |
edited tags
|
|
| Jan 6, 2012 at 18:44 | comment | added | agent86 | @Jonathan. I rent the IP as part of a VPS package, and this is the one and only app running on it and accessing the stack API. I had problems earlier this week where my quota was decreasing even though I wasn't using it, so I'm betting this is another bug along those lines. | |
| Jan 6, 2012 at 18:27 | comment | added | Jonathan. | Do you have any other apps using the API running on your IP address (maybe on another machine on your network)? Try generating an access token for you on your app and putting that in the query, if the request returns normally, then the problem is not your app or the API, but another program using API. | |
| Jan 6, 2012 at 17:29 | comment | added | agent86 | @Jonathan. I added the additional data requested. In testing prior to the throttle violation, I had 10k as my max quota. I've also included the usage graph that shows I'd gotten to about 300 on the 5th before the violation kicked in. | |
| Jan 6, 2012 at 17:27 | history | edited | agent86 | CC BY-SA 3.0 |
added 542 characters in body
|
| Jan 6, 2012 at 17:00 | comment | added | Jonathan. | Also you are including your application key in the request right? If you don't the request quota is only 300, compared to the 10,000 you get with a key. | |
| Jan 6, 2012 at 16:59 | comment | added | Jonathan. | On the homepage of Stackapps, on the left click Manage Applications, choose your app, then on the left click Query Statistics, this will provide you with a graph to show how many times the method has been requested and when. If the graph doesn't explain the problem take a screenshot and post it in your question. | |
| Jan 6, 2012 at 16:42 | history | edited | agent86 | CC BY-SA 3.0 |
added 165 characters in body
|
| Jan 6, 2012 at 15:43 | comment | added | agent86 | I'm now making requests once every 2 minutes, and I'm still getting nothing but 503 errors. It seems like I should be able to make multiple requests per second without hitting the throttle limits, so any input would be most helpful. | |
| Jan 6, 2012 at 2:18 | history | edited | agent86 | CC BY-SA 3.0 |
added 28 characters in body
|
| Jan 6, 2012 at 1:59 | history | edited | agent86 | CC BY-SA 3.0 |
moved debug requests to another question
|
| Jan 6, 2012 at 1:34 | history | asked | agent86 | CC BY-SA 3.0 |