Why? We don't need "real time data". I mean, we just need something like currentActivity (activity, fireteam, opponent etc... just a few data) and it can be write as soon as the activity started rather than at end as they do now

Ah, my mistake - when you said "current (real time) activity" I thought you meant real time data. So if you get character info, the character's currentActivityHash property should be the hash of the activity they're currently playing. The /Platform/Destiny/{membershipType}/Account/{destinyMembershipId}/Character/{characterId}/ endpoint can get you that info, or if you already use one of the other "get character" endpoints it should be under result.data.characterBase.currentActivityHash. Hopefully this helps!

yes, but with currentActivityHash property can I get my fire team member and the opponent member of the current activity? Where I can get it? I mean, if I don't have an activityId (or instanceId) how can I get these info? thanks and sorry for my poor english :-)

No worries! Oh, I see - sadly we don't get that kind of data down the pipe to us in regards to fireteam or current opponents. Some of those details are handled by a different set of servers internally that BNet doesn't have access to currently. But I will bring it up: I could definitely see interesting use cases for being able to get at that data! I don't know how difficult it would be to get BNet access to that data however, so I can't make any promises. But if we manage to actually get at this data, this forum will be the first place that finds out! EDIT: However, looking into it further, we might be able to plumb through at least the Fireteam data. I need to investigate it further, but at least some of it might be more feasible than I realized at first. If anything comes to pass from these investigations and we plumb that through, I'll make sure to let the group know.

Thank you. I will be very happy to know it