forums.rs

Forums

Ridiculous state of API's

Quick find code: 351-352-33-65383759

of 2
Deathslayer
Jun Member 2006

Deathslayer

Posts: 854 Gold Posts by user Forum Profile RuneMetrics Profile
I somehow missed the part of the original post regarding obtaining a previous username of a player. For those fansites amongst us who have statistics trackers or similar features, this would be immensely useful, as it would let us automate what's currently a sketchy or arduous process of verifying name changes.

Whilst I can understand the security or privacy implications of providing all past names, the latest name change within the past 35 days is essentially public information to anyone in-game, as it can be obtained even if the target player has you on their ignore list. It stands to reason then that any name changes within the past 35 days would be an OK thing expose on a public API - either an existing one, a new one, or just simply added to the Adventurers' Log profile.

I'm well aware that there may be problems with the ability to obtain this data, I'd personally love to see this feature implemented, as it would make life so much nicer for both myself and fellow developers.

04-Jun-2014 23:34:55

Ryan M
May Member 2008

Ryan M

Posts: 3,095 Adamant Posts by user Forum Profile RuneMetrics Profile
GE API Obj:
http://services.runescape.com/m=itemdb_rs/obj_big.gif?id=31519
http://services.runescape.com/m=itemdb_rs/obj_sprite.gif?id=31519

Runedate of last system update:
http://services.runescape.com/m=itemdb_rs/api/info.json

Some good points nonetheless. :)

05-Jun-2014 08:21:46 - Last edited on 26-Aug-2014 12:46:48 by Ryan M

Mod Boko

Mod Boko

Jagex Moderator Forum Profile Posts by user
Hey guys!

We introduced the API’s to help reduce load on out servers and to limit the possibility of the brute-forcing of restricted information. We would acknowledge that it is probably more restricted than it would be ideally, but it was added as a nice extra and was never intended to be developed as a mature, fully featured API feature. The restrictions that are in place are there because of load concerns which are still very active, with about half a million hits for itemdb requests in less than 48 hours and a total number of 112 million page hits in that same period.

We are going to be looking at APIs, including retrieving more statistics on usage and developing an understanding of how it is being used, with an eye to shaping future development and building more appropriate tools.

The seasonal hiscores were developed with a deeper understanding of the design requirements and the importance of API support is an underpinning of new systems or reworks going forward. Some of the restrictions will remain severe though given the continual load that is placed on our systems through the API, itemdb being the most constant example. @jagexboko #justblameboko #fsdfs

13-Jun-2014 08:50:17

Skillbert
May Member 2008

Skillbert

Posts: 392 Silver Posts by user Forum Profile RuneMetrics Profile
Thanks for the reply Mod Boko, I'm glad to see that the team is working on a solution. Please consider involving the people on this forum as we are the people that will be using it. There are plenty idea's and requests on this forum that would lead to effective and efficient api's.

Deathslays idea for example would add a very small of extra load for the ge price update system and turn all current ge bruteforces into one single request to a static file of less than one mb.

16-Jun-2014 15:34:40 - Last edited on 16-Jun-2014 15:34:55 by Skillbert

Quick find code: 351-352-33-65383759 Back to Top