Too many requests.. Question?

When my APi hits the big 100

Too many requests
The current private key is banned for a small period of time because of too many requests (max 100 per minute)

Do I have my program stop for 5 minutes (hang in a timed loop, this isn't a good idea)

or

Keep then program running calling the API's until the Too many requests error has gone

I'm not sure what I should do, are we allowed to keep calling the API after the key is banned



Just a Note, I am handling API call rate, this only happens when I run a second API program

we really need an API call counter in the API's so this wouldn't happen

we are all running more API Scripts and Programs there is no way of knowing the call count

Adding a call count in USER BARS might help, if it can be done

{

"server_time": 1521759204,

"callrate": 5,

"happy": { "current": 4396,

"maximum": 4500,

"increment": 5,

"interval": 900,

"ticktime": 396,

"fulltime": 18396

},

ha ha ha ha, I fell over laughing

1 cal a minute, what world do you live in, do you even use APIs DocTorn default is 12 calls a minute

and do you think you can do anything with 1 call

stop patronizing me and Bug OFF

Dunno if this is a bug or not but if u reset your api key the ban goes away

probably is a bug - bet they ban the key by literal key, not by player id or something

interesting.. lol

I am doing pretty well at controlling my API Calls under 100

[image: i62.servimg.com]

This 5hr Graft highest hit is 28, considering all the stuff I'm doing in this app it is fanatically low



But I'm am still having problems that can be avoided when testing other API's apps while this one is running

If only we knew what our call rate was.



and an apology:

I'm sorry Bug, for being so harsh

but really I do know what I'm doing and call counting is one them

I've already asked for a rate limit header in the past but was mostly ignored...

This is pretty standard on APIs nowadays:

https://developer.github.com/v3/rate_limit/
https://discordapp.com/developers/docs/topics/rate-limits
https://developer.twitter.com/en/docs/basics/rate-limiting
https://developer.vimeo.com/guidelines/rate-limiting
https://auth0.com/docs/policies/rate-limits


While one can (and should) control their own API usage, you never know what other apps the user has running and if you should stop to prevent going over the limit. Trust no one!

I have found a simple solution for API request calls, over many different API applications running at the same time

The idea is that calls are saved to one central place for all API's to read and update

the API request count is saved on the PC with

SetSetting($section,$key,$value) and retrieved with GetSetting($section,$key)

a second Setting for Calls per minute,

SetSetting($section,$time,$value) and GetSetting($section,$time)

if the time has been over 1 minute since it last read (by any application) then set it to zero and save the new Time

.

this makes it possible for any number of API's running to

• Read the request count
• Read the Time last reset
• Reset the Count, if 1 minute has passed
• Test call_limit(100) has been reached
• Increase and Save New Call Count

this works for me,

.

maybe all API applications can do this, by having one Set location for Calls and Time

a Global Standard Setting would have to be used by all APP's using the same data

examples:

SetSetting("TornAPI","CallCount","0")

SetSetting("TornAPI,"ResetTime",$Unix($date))

GetSetting("TornAPI","CallCount")

GetSetting("TornAPI,"ResetTime")

someone could probably think of better names, but its out there

.

no one will fail with too many calls again.

Here some tip.... maybe you find it interesting.... You cant control shared usage of API key with other applications, but for most of them you can know how much call they use, for example if you set DocTorn to refresh every 5s it will spend 12 calls per minute, so you have 88 more for your app.

Thing that you can do is same as what game developers use to limit FPS of game, but you instead of limiting Frame Per Second you will limit API Per Minute. At the end you just need to set up how many API call you wonna you app to use, at this example I would say 80, to leave 8 call for backup, to use them for some manual calls when i wonna check something while flying that's not on app.