Include follow count in /helix/users
Add follow count to /helix/users endpoint. This data is accessible via /helix/users/follows, but would require an additional call.
Just chiming in with a bump - this would be great and seems like an obvious win for the servers as well as the clients.
Any updates on whether this is going to be added?
Yes, indeed! I also really miss this while switching all my old stuff to helix.
Antonio Martínez commented
Same here, until we have an alternative we cannot stop using the v5 method and update the API client.
Looking forward to an official response :)
Agree, right now with the new API I have to make a lot of additional requests and my program is running so slow, not speaking about rate limits, in comparison with simple method from v5 API "channel list" with followers count right in a response.
And I've got email about v5 turning off (as many of you) without proper solution to upgrade, not loosing performance in tens times.
Could we have an official response as to whether this will be addressed before v5 API is shut down?
The extra calls needed to just grab the total are timing out my serverless cloud functions when ran on channels with big user lists. I am trying to sort a channels followers by their own follows, since I can't batch up requests, it is taking a long time to call all the API calls.
Just to throw my cents into this one, having the follower count in the users response would be extremely useful and would save a huge number of additional API requests.
For example, if you wanted to show a list of channels within a team, you'd now need to make a request per channel when previously you could do this in a single action.
it would be awesome to see that!
Wow, it really should be added already, very useful
Hope to see it asap
I'd love to see follows number in the users API endpoint (https://dev.twitch.tv/docs/api/reference#get-users), but if this is not complicated it would be great to have it also in Streams API response( https://dev.twitch.tv/docs/api/reference#get-streams).
Such improvement will decrease additional API calls, so its a win-win for developers and for API too :-)
I agree with this.
Also calling to /helix/users means you request more than one ID at a time unlike /helix/users/follows which only accepts one user per request and so gets quickly rate limited