Query data from an Xuid rather than a Gamertag

Xuid’s are static, and don’t change. Whereas Gamertags can. Being able to store xuid’s on the backend, and use those to query data would prevent a large number of breaking changes to datasets.

The Xbox Live api had a pretty neat method of allowing users to specify Xuid or Gamertag. For example:
http://service.xboxlive.com/path/gt({player-gamertag})/settings - for gamertags
http://service.xboxlive.com/path/xuid({player-xuid})/settings - for xuids

Would this be a feasible thing to add to the API? It would be greatly appreciated.

I raised this during the previous beta. I never did hear back on the issue.

You can see that there is a XUID property on some of the responses, but it’s always nulled out. It looks like they could support responses quickly, not sure about changing queries (which would be better).

They can’t make this available to us, I’ve already pinged them on it. The api devs know our pain :slight_smile:

> 2533274825844169;3:
> They can’t make this available to us, I’ve already pinged them on it. The api devs know our pain :slight_smile:

Did they give you a reason behind this? Just wondering what the policy MS has on hiding xuid’s is.