{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
originally posted in:BungieNetPlatform
12/16/2015 10:49:30 PM
2
Issues with /Character/{characterId}/Inventory/ being deprecated as the new one is missing data.
Hi. The docs claim /Character/{characterId}/Inventory/ is deprecated and /summary should be used instead. However that end point does not have all the data the old one has. Specifically it won't tell you what perks have been selected on weapons and armor. I think it might be missing something else like gridComplete as well. I notice bungie.net gear manager does show the selected perks. I hope you are not using the deprecated end point! Seriously though, will the missing data be added to the new end point?
-
7 RepliesThey are trying to reduce the size of the request (since the new one will return ALL your items) and are encouraging developers to implement a system where you are only requesting for more information about a specific instance when the user inspects it.
-
4 RepliesI can tell you that my app was using the old endpoint a few months back, and as soon as they released the new one i switched my app to work with that one, and as you can see there are good things and bad things about this. GOOD: - It requires less calls, you get every single item that you have in one call instead of 4 as it previously was. - Is faster, most of the positive feedback i get is that my app is the fastest item manager - To make the call you need less info (you don't need to first get the characterIds to then make the call, they will come as part of the call) BAD: - You don't get all of the info, even some that might seem as required like the perks and stats - Because is public endpoint, if your credentials are no longer valid it will not say that you need to log in, instead they just remove the token from the headers on the response, which makes your code to have to check for the login error plus the headers But, my next move is to move to a Hybrid call, i'll the summary endpoint to get all your items, and only if i'm missing the FULL description of an item, then i'll use the old end point to get all the info, this should minimize the times i have to use the old one but, without losing the info.
