{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
originally posted in:BungieNetPlatform
Edited by VThornheart:
9/14/2015 6:51:22 PM
12
IMPORTANT: GetDestinyAccountSummary will become GetAllItemsSummary
UPDATE: The fix to provide all character data will be going in later today! Keep an eye out for updated services.
---
GetDestinyAccountSummary was a prototype service, and now that we're settling down and preparing for its official use we're renaming it to more closely reflect its intent.
GetDestinyAccountSummary [b]will become GetAllItemsSummary[/b], to better reflect the intent of the service and free up the name for a GetDestinyAccountSummary service that actually *will* be an account level summary service call.
The [b]endpoint will become {membershipType}/Account/{membershipId}/Items/[/b] instead of .../Summary/
The expected inputs and outputs aren't intending to be altered at this time. I'll make another reminder as we get closer to release, so you know when we're going to make the changeover, and if there are other changes to the service I will keep you up to date in this thread. Currently we're anticipating this will go live on the 8th, but I will keep you posted. Stay here for updates.
-
2 RepliesThis endpoint allows for a simple and fast view into a user's items, but you aren't able to determine what items are equipped (which is important for item managers). There are references to item hashes in the equipment field for each of the characters so it's pretty much already there. Is this endpoint is ever going to expose that information?
-
8 Repliesi have a question, is it me only or sometimes the guardians order and the index on the item, do not match ? cause i have seen a few times and 1 of users reported this as well to me, that i see the items of the other character into one character. And because of that, everything you try to do with the item will fail saying it couldn't be found. If no one have seen this then it means is my bug at the time of mapping everything (Which anyways i'll check once i have time).
-
6 Repliesfrom just one day of the update being on the wild i can tell that 50% of the errors reported in my dashboard are that i tried to equip an item that they don't have the level for yet. And, this is because i try to find a good item to equip instead of the currently equipped one, so that they can transfer it from the other character, but, without this data, i can't reliably choose an item :(
-
1 ReplyFrom what i can see, IS OUT ALREADY !!!! :) the hype is real, tonight just to check if everything is working as expected and add the new "types" of items to my database
-
8 RepliesThe update will take place later today that should correct this issue. Thank you, and my apologies on the delay in being able to use this new service!
-
5 RepliesI'm only getting the items in my vault. Intended?
-
8 Repliesany update on the time of the release of the API ? to be able to test and then release the update :) very hyped about the new end point.
-
3 RepliesAnd is there going to be something as well for "equipable", like if is an engram, how to tell if you can actually equip this or not ? Cause my app that's the issue i'm having, that if you have an engram it tries to equip that cause it satisfies all the other restrictions.
-
Any other change since last time ? So that everything is working by the 8th and i can just push the update with out problems :)
-
1 Reply
-
2 RepliesMore changes: * the "locked" property will be removed from the item summary objects. * It will be replaced with a more compact/useful "state" property, which is a Flags enumeration of type ItemState, which has a few potential initial values and will likely expand as new features come about: None = 0, Locked = 1, Tracked = 2
-
1 ReplyThanks for the heads up. I'd much rather be proactive than reactive when the /r/DestinyItemManager sub blows up with issues after maintenance windows.
