Rate limit changed?

12/28/2021 at 6:07 AM

Hi,

Lately, I have noted that sometimes the X-API-Rate-Limit header tag(s) is / are missing from returned data, and sometimes I get a new data section that indicates errors like this

{"error":{"type":"OAuthException","message":"Invalid access token"}}

{"error":{"type":"ApiException","message":"Rate limit exceeded."}}

I have not found any documentation indicating these changes.

What have I missed?

/ Kenneth

12/28/2021 at 8:30 AM

Ping Mike Stangel or someone who knows

Private User

12/29/2021 at 9:01 AM

Mike have vacation

12/30/2021 at 9:56 AM

Thanks Björn!

I haven't seen those unusual responses for the last day or so, so I'm not sure what the reason might have been....

Private User

12/30/2021 at 12:20 PM

Both error messages is clear enough and is explained in the documentation. Rate limit depends on connection, but the X-API-Rate-Limit header is not needed except for monitoring to slow down before you hit the limit - just catch the exception and resend the request after a couple of seconds. It is however some time since I used the API so things might have changed.

12/31/2021 at 1:14 AM

I agree that they are clear enough, but I have not seen any explanation in the documentation them. Can you point me to where they are explained, please?

Rate matching was only handled using http-headers and null-data as I have understood it, but now it seems like we may receive json-coded error information as data contents as well.

/ Kenneth

12/31/2021 at 1:24 AM

I can also mention that I have updated my rate matching code in the last few months to get better average throughput. Maybe those changes have affected something...? Now I try to get as close to the rate limit as I can without exceeding it, using the http-header-info.

3/10/2022 at 5:35 PM

Kenneth Ekman

Have you noticed that the rate limit appears to have been slashed from 10 per rate window (10 seconds) to 1 per rate window in the last few days.

This has now ruined my application and is unacceptably slow. This has been done with no warning or communication - I am hoping that it is only a temporary measure due to some unexplained event?

Private User Mike Stangel - you guys appear to be authorities on the API, do you know what is happening?

3/11/2022 at 8:42 AM

Kenneth Ekman we are now giving different API rates to new / unapproved apps vs. approved apps. We need to approve yours, however I see you created three! Which app ID are you using, and can I delete the other two?

3/11/2022 at 8:43 AM

Kenneth Ekman correction, I see 5 apps registered to you.

3/11/2022 at 9:36 AM

I'm using the one named WebTreeView (433) currently. The other ones are not used.

3/11/2022 at 2:44 PM

Kenneth Ekman Your app has been approved.

3/11/2022 at 3:16 PM

Craig Andrew Miles what's your app ID? I'll take a look and approve it, as well.

3/11/2022 at 9:56 PM

Thanks so much for the swift reply Mike Stangel

The App ID I am using is #536

Incidentally, all of the other Apps (#532 to #535) were created "accidentally" due to my uncertainty about what was going on in the registration process although admittedly that was a while ago now.

I just tried the "Delete Application" link and it still doesnt work which was my original problem. Just gives an "Error: Page or Resource Not Found" message. The actual URL (for eg #532) is https://www.geni.com/platform/developer/apps/532 which may mean that this is a permissions error as it looks the correct URL.

Anyway I would be most grateful if you could approve App #536 and happy for you to delete #532-535 if you are so inclined. They all have the same name!

3/12/2022 at 5:08 AM

Thanks Mike Stangel

3/15/2022 at 6:42 AM

Hi Mike Stangel

I was hoping you would be able to approve my App #536 sometime soon if possible.

Thanks

Craig

3/15/2022 at 8:59 AM

Craig Andrew Miles - done!

Juha Mustonen (Geni Curator) C

3/15/2022 at 4:03 PM

That's great. Thanks Mike Stangel

3/16/2022 at 11:21 AM

Mike Stangel could you approve also my apps #455 & #412.

3/16/2022 at 2:08 PM

Juha Mustonen (Geni Curator) Done.

Michael Shalom Fagan PRO

3/28/2022 at 6:19 AM

Any chance mine can (#550) get approved as well? It's still in development, not public... not sure if that matters.