Because the two activities have some fundamentally different properties, we'll be splitting it into its own property (still under the same endpoint). Response.data.elderChallenge will have data specifically for the new POE "Challenge of the Elders" mode. It will take the following form: { playlistActivityHash: 0, // Activity hash for the Playlist, if you care about that sort of thing activityHash: 0, // Activity hash for the actual activity, which has skulls and such on it iconPath: "something.png", rounds: { // Same as the old POE rounds structure. But there will only be 3 rounds, and each will have a "bossCombatantHash" and "bossLightLevel" property. The former can be used to look up combatant info (their name, associated image, etc...) in the Combatants definition database. }, objectives: { // Mirrors the current "objectives" data that we return elsewhere, but specifically for POE Challenge of the Elders }, hasTicket: true/false, ticketItem: { // A DestinyInventoryItem instance for the ticket, in case you wanted its details. }, bounties: { // Mirrors the current "bounties" data we return elsewhere, but specifically for POE Challenge of the Elders }, playlistSkullIndexes: [ ], // Indexes into the non-score-bonus-providing Activity's skulls playlistBonusSkullIndexes: [ ] // Also indexes into the Activity's skulls, but specifically for skulls that provide score bonuses }