Hey everybody!

I am going to be honest and plain in this update, I misunderstood how they could rate limit me, and this post is a result of that. I made a mistake and thus the post below me stays the way it is to not hide from it. If i offended anyone in any way, i'm sorry and it wasn't my intention. I was shocked by the logging I received and wanted to address this issue. Thanks my fellow redditors for pointing me my mistake!

I'll do better.

So i want to address something really serious that i've noticed last night. Which is the error 429 the API has been throwing, and also 522.

Basically what this means in non-technical terms, Jagex attempted to rate-limited the public API.

Technical

After the initial 429 "too many requests" error, the servers started to throw a "503 Service Temporarily Unavailable" quickly after. I haven't missed these responses because i keep all responses in my own logging system.

This could mean a multitude of things for example:

- Jagex tried to update the API with a rate limit and quickly noticed they deployed the changes, so they quickly made the server temporarily unavailable.

- Jagex made updates to the API without informing anyone about them, meaning no logs, nothing.

- The Jagex servers couldn't keep up (which I highly doubt)

I have noticed that the returning headers also changed, meaning they configured how long a response will stay alive, meaning no more sporadic XP updates, but set intervals instead.

One thing is for sure here: They are not happy with the recent attention the public API has been getting and are up to something shady. You can't hide from a logging server Jagex....

We should get a JMod to explain what they did to the API, maybe it's something good, maybe it's not. We don't know and they should communicate.

External link →