Realm Status API Inconsistency Consideration

Community Platform API
Post Limit:
Hello, just wanted to make a suggestion. Was doing a comparison between realm and the the API URI requests and noticed a little inconsistency.


Now:
http://{region}.battle.net/api/wow/realm/status?realm={realm_name}

Compared to:
http://{region}.battle.net/api/wow/character/{realm}/{name}?fields=

And:
http://{region}.battle.net/api/wow/guild/{realm}/{name}?fields=


What I am thinking:
http://{region}.battle.net/api/wow/realm/{name/all}?fields=status


My thinking on this is the URI paths is divided into categories:
api/wow/realm
api/wow/character
api/wow/guild


Depending on the type of categories, I might need to follow an API path that contains parameters.
api/wow/character/{realm}/{name}


This in my opinion is where the realm URI request inconsistency occurs. I think for the future having a fields request makes more sense in context with other API examples. With a status as an option everything is more consistent. Later things could be added like Battlegroup, Realm Type, ect. to pull more specific information. Maybe we rather not pull the status at all, to make the point.

Hope this is constructive. I am a little new, but not too new, heh :).
i would save your speculation an criticism until the official API documentation is released on Tuesday.

Join the Conversation