That's correct. Optional fields aren't returned unless requested. |
We'll try to get quests and profession recipes in. |
As previously announced, we are planning to expand the Community Platform API with feeds for the 3 different types of profiles currently available on the website: characters, guilds, and arena teams. We’d like to share our current plans (may change, not a promise) with all of you as we look forward to providing a robust API that meets the needs of the community.
Each of the feeds below will be accessed by using a realm and name. The feeds will always contain basic information by default, and will have optional fields that can be requested via a parameter – making it possible to retrieve all the data in a single request. A locale parameter will also be available for localized strings. In addition, the feeds will support the Last-Modified HTTP header to help with caching. Just like with the realm status feed, region will be specified using the subdomain (e.g. eu.battle.net/api/.. for European realms), and both json(p) and protocol buffer output will be supported. Character
Guild
Arena Team
Optional fields would be requested using the ‘fields’ parameter, where you specify everything you need using a comma-separated list. e.g: /api/wow/character/realm-name/grotako?fields=items,talents,mounts,titles Sample feeds will soon be provided as we’d also like feedback on the data format. In the meantime, let us know what you think! p.s: We’ll have more details on the Auction House and Arena Ladder APIs to share in the coming weeks. |
We have recently deployed a fix that should resolve the issue. Please let us know if you see it happening again.
|