Any news on this? When rolling through all subscriptions to calculate the sub points count, it normally produces an incorrect number compared to what's on the dashboard

I would never understand why there is not this total field in the return of the first call.

For a channel like the one I manage, I need no less than 100 calls to go through the streamer's 10,000 subs and count them.

And that every 5 minutes. It takes 40 seconds of looping request whereas a simple total field would have avoided this abuse.

Two years after the first forum posts on this matter and here I am voting for it.

I'm very surprised that Twitch Entertainment Inc doesn't give the API higher priority. I say this as a WordPress plugin developer (TwitchPress) involved in supporting many streamers to create bridges between their own site, Twitch and social networks.

It means my work helps many streamers and doesn't fill my pockets with money either. If I see a need in the API it is driven by many streamers (many affiliated) from all levels.

Everything's pretty much already covered in the comments here, but just adding another voice here. Sub count, and more importantly sub points, are so important to motivating viewers to sub and get their favorite streamer to the next emote slot, and there's still no accurate way to do that with with Helix. Adding up all sub points based on the subscriptions endpoint is not accurate if there are permanent subs or if anyone has upgraded their sub tier in the last month.

For overlays, goal bars, counters, etc. The data from the streamer dashboard, would be a huge help in Helix. The dashboard endpoint returns the following JSON.

{
"count":1,
"score":1,
"count_breakdown":[{"plan":"1000","count":1},{"plan":"2000","count":0},{"plan":"3000","count":0}],
"score_breakdown":[{"plan":"1000","score":1},{"plan":"2000","score":0},{"plan":"3000","score":0}],
"next_level":{"minimum_score":15,"emoticon_limit":2}
}

Sub count, but also sub score is important for many streamers to be able to show their next goals.

The sub score in particular to be able to show the next step for unlocking additional emote slots.

Having this behind a specific broadcaster's authentication (scope) would also allow it to retain its needed privacy.