WoW Game Data and Profile API Patch Notes - 2019/12/10

API Discussion
1

Hey y’all,

We have some bug fixes coming your way with the weekly reset on 2019/12/10 or 2019/12/11, depending on region. Without further ado:

WoW Game Data and Profile API Patch Notes - 2019/12/10

Specialization Talents

/data/wow/playable-specialization/{id}

  • Added talent_tiers.tier_index field, a zero-indexed value indicating the tier of the sibling talents.
  • Added talent_tiers.talents.column_index field, a zero-indexed value indicating the column that the talent is in.

/profile/wow/character/{realm-slug}/{character-name}/specializations

  • Added specializations.talents.tier_index field, mirroring the above.
  • Added specializations.talents.column_index field, mirroring the above.
  • specializations.talents array will now be ordered by specializations.talents.tier_index.

Character Achievements

/profile/wow/character/{realm-slug}/{character-name}/achievements

  • Endpoint will respect the Display Only Character Achievements To Others in-game option, found in-game at Game Menu | Interface | Social | Display Only Character Achievements To Others.
  • Data returned will reflect achievements viewed in-game when inspecting another character.

Pocket-Sized Computation Device

/profile/wow/character/{realm-slug}/{character-name}/equipment

  • Pocket-Sized Computation Device will now show the correct item level.

Mounts

/data/wow/mount/{id}

  • Mounts will now show their faction correctly if they are faction-specific.
  • Many older mounts will not have a faction. Instead, they will have a should_exclude_if_uncollected boolean value indicating that the user interface in-game does not show the mount unless it is collected. While we realize this is not ideal nor explicit, it’s an artifact of how the game represents older mounts.

Hunter Pets

/profile/wow/character/{realm-slug}/{character-name}/hunter-pets

  • Added hunter_pets.creature_display field, indicating the display that the Hunter pet is using for this character, as many Hunter pets have multiple possible displays depending on which pet was tamed.

Pets

/data/wow/pet/{id}

  • Added creature field, a reference to the creature for this pet.
  • Removed creature_display field. This field was showing invalid data, as pets have more than one display option. Instead, you should fetch the data from the new creature field, then use the creature_displays field from the returned result. This change is backward-incompatible.
  • is_random_creature_display added, a boolean value indicating whether or not the creature display for this pet is random every time the pet is summoned.

/profile/wow/character/{realm-slug}/{character-name}/collections/pets

  • pets.id added, a unique ID for each pet. This value is the base-10 equivalent of pets.collected.battlePetGuid from Community API.
  • pets.creature_display added, indicating the display that the pet is using for this character, as many pets have multiple possible displays.
    • This value will not be present if is_random_creature_display from the above endpoint is true.

Other Information

  • Profile endpoints (/profile/wow/**) will update when the character logs out of World of Warcraft. Older character profile endpoints will not be updated to include these bug fixes; characters must log out of the game to be updated.
  • Data endpoints (/data/wow/**) will update automatically on or about the weekly reset using the static namespace for each region (static-us, static-eu, static-kr, or static-tw).
  • The pet endpoint contains a backward-incompatible change. We apologize for the inconvenience and hope to minimize these changes in the future.

Thanks!

Araspir

7 Likes
2

Great example of very helpful patch notes, and even more bonus points for getting the notes ahead of time. Thank you!

4 Likes
3

This is all fantastic news, thank you! :slight_smile: