{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
originally posted in:BungieNetPlatform
View Entire Topic
Edited by Icysoulspark:
2/12/2016 10:43:00 PM
1
Which of these endpoints to use for Character level details?
As per the list of available end-points at https://www.bungie.net/platform/destiny/help/, there are two possible options to get character-level details for a given account:-
1. /{membershipType}/Account/{destinyMembershipId}/Summary/
2. /{membershipType}/Account/{destinyMembershipId}/Character/{characterId}/
What's funny is that #1 also contains all the details of your characters, including per-character stats and all cosmetics required to render your guardian. Is there a particular decision point that enforces one choice over the other? One scenario I can think of is when an application chooses to display all of your characters on the same page as the main account info (option #1). This will result in fewer server roundtrips hence saving the network bandwidth consumption for the user of the app (on a mobile device + out of wifi coverage) but for a web-based tool, this might not apply.
Any other criteria to consider?
-
1 ReplyI would recommend the Summary, in one call you get all the guardians and their inventories (also vault inventory). The reason why is because if you want to use the second one you will have to first make another call to get the list of characterIds that the account has, and then do up to 3 (if they have 3 characters) separate network calls to get the info, which means that you also have to handle the synchronization of those 3 calls, so that you wait until all of them are done in order to finish (Which is not hard, but tedious). In other words 1 network call against up to 4 network calls. Is better for you and better for Bungie's :)
