Multiple fields on new WoW Profile API

API Discussion
1

Hello,

I have a major issue about the migration API.

Currently, I use the following endpoint to retrieve data from wow character profile :
https://{region}.api.blizzard.com/wow/character/{realm}/{name}?fields=guild&fields=items&fields=pvp&fields=statistics&fields=achievements&locale=en_GB&access_token={token}

With the migration, this endpoint is replaced by multiple endpoints :

  • /profile/wow/character/{realm-slug}/{character-name}/equipment
  • /profile/wow/character/{realm-slug}/{character-name}/achievements
  • /profile/wow/character/{realm-slug}/{character-name}/pvp-summary
  • /profile/wow/character/{realm-slug}/{character-name}/statistics
    …

Is there any way to make only one call with the new API?
If anyone has a solution, I’ll take it :frowning:

Hirokumi

1 Like
2

With the new setup, you will need to hit all of the endpoints listed. There is a lot of conversations about the increase in hits for data at a per-character level.

3

Performance wise, I mitigated the per-character impact by making my data collection layer fully parallel. Feeling like I needed to do that is another reason this was not a painless transition for me. The new APIs do feel faster to me than a heavy weight old one with multiple topic requests, so you might break even there.

Of course that does nothing as far as helping with the request rate limit. The devs have said they are watching what is happening there so I guess the advice is do what you need to do and plead for mercy if you need it.

1 Like
4

If I have to make 10 requests to get the data I want for a character search, I couldn’t do more than 3600 searches per hour, or more than 10 searches in one second, during peak hours it’s already happened.

And I’m not talking about missing data compared to old calls.

I must admit that this migration is very scary for me.

2 Likes