v3.7

Related endpoints

• GET /guild/{query}
• GET /guild/prefix/{query}
• GET /guild/uuid/{query}
• GET /player/{username}
• GET /leaderboards/{lb_type}
• GET /item/database
• GET /aspects/{tree}

Guild endpoint

We are expanding the /guild endpoint to contain more data, the below list contains the new fields included in this update.

Main guild stats

• totalGuildRaids > All raids completed by the guild, including raids done by players that are no longer in the guild.
• ranking > Current guild ranks in leaderboards, except legacy territory, level, and wars leaderboards because those are still calculated on request.

Per-player stats

• lastJoin
• wars
• globalData > Same style as player main stats global data.
• weekly > Weekly completion and streak data.
• playtime
• restrictions > Access rules affecting the guild member payload.

weekly is empty when restricted. It uses this structure when visible:

1
{
2
  "weekly": {
3
    "completed": true,
4
    "streak": 3
5
  }
6
}

Guild member restrictions include:

• online_status
• main_access
• weekly_access

guildRaids and playtime are inside globalData. guildRaids in guild member stats only counts raids done inside the current guild, while player stats keep the global value.

Player Stat & Guild history

Since it was confusing, we have made it so player stats don’t use deleted characters data anymore.

And since guild raid data is now being stored per guild instead of globally. This allows a new guildHistory field to exist in player main stats.

guildHistory only contains guilds where the player has completed at least one guild raid. A new access rule, guild_history_access, controls access to this field.

We have also added raidStats, an object that contains various stats about raids (damage taken/dealt, healing, etc…)

1
{
2
    "raidStats": {
3
        "damageTaken": 180569,
4
        "damageDealt": 186268752,
5
        "healthHealed": 251434,
6
        "deaths": 11,
7
        "buffsTaken": 63,
8
        "gambitsUsed": 0
9
    }
10
}

Leaderboards

The patch includes a leaderboard rebuild to improve accuracy and performance.

• Fixed XP, total level, and related leaderboard issues.
• Fixed guild raids being absent when a player renamed.
• Fixed players staying in guild data after leaving.
• Fixed the Fruma raid not being registered by the API.
• Fixed Guild raid-related leaderboards including rank and restricted fields
• Added a proper leaderboard for the new raid.
• Added guildTotalRaids, ranking guilds by all raids completed by the guild, including raids done by former members.

Items and aspects

Ascended items require a response format change. Item endpoints now return an array of item objects instead of an object keyed by display name.

Previous format:

1
{
2
  "displayName": {
3
    // ITEM
4
  }
5
}

New format:

1
[
2
  {
3
    "displayName": ""
4
    // ITEM
5
  }
6
]

Aspects follow the same array-of-objects format and now include internalName:

1
[
2
  {
3
    "displayName": "",
4
    "internalName": ""
5
    // ITEM / ASPECT
6
  }
7
]

This should fix invalid controller counts and missing ascended items.

Performances

This update also brings optimizations to players and guilds rendering which should speed up the API globally; it also means we are removing the authentication-lock that was applied to the fullResult query parameter last patch.