Chatters / Viewers Helix API Endpoint
The existing API endpoint for getting chatters predates User IDs and only returns usernames. It's also part of TMI and not officially documented, which could result in it being removed at any point without any notice.
Many bots use the endpoint for channel loyalty points, and then have to make secondary calls to the get the user ID.
TheElm
shared this idea
We are actively reviewing the use cases that were shared in the quarterly survey that closed on August 1. 72 developers provided feedback for this question, which we greatly appreciate! This will help us understand the best design for such an endpoint. Given this research, we will move the suggestion into "Investigating."
-
We are actively reviewing the use cases that were shared in the quarterly survey that closed on August 1. 72 developers provided feedback for this question, which we greatly appreciate! This will help us understand the best design for such an endpoint. The functionality would focus on chatters, i.e., users that are connected to chat. Given this research, I will move this suggestion into "Investigating."
I'm not sure I follow point #2. Do you mean providing userids with the call to see if those specific users are connected to chat or something else?
-
Scymplex
commented
Any updates on this?
1. Making the chatters list an official API GET endpoint.
2. Possible inclusion of userids.
3. An optional parameter to get viewers instead of chatters. -
We've added a question regarding a chatters endpoint to the latest quarterly survey. If there are additional thoughts or use cases beyond these comments that you would like to provide, please feel free to add those notes to a survey submission and it will be passed along. https://twitter.com/TwitchDev/status/1542995359122989056
-
Matty_TwoShoes
commented
6th most-voted idea in this section and there hasn't been a single update from Twitch regarding this. Come on Twitch!
-
maxmarrie
commented
I think its not a official way to use these API keys. You need to buy original API keys then you have to use it. I also did the same thing for my website https://www.travellersquest.com/blog/mountain-biking-in-nepal/.
-
Scaylet
commented
This is a really needed extension to the TwitchAPI. My loyalty system is currently using current chatters endpoint, but that approach is excluding lurkers. They are just as important so it's sad to see there's no official way to get that data.
-
mori_maxw
commented
I can't believe there isn't an official, documented solution for this in 2022. Twitch, this is urgently needed, especially as we move towards community-driven creator ecosystems where seeing who is active and who isn't is key.
-
pjonp
commented
This endpoint should no longer exist.
It should have never made it to v5 and I'm perplexed how an open endpoint that shows all of the viewers in chat is still active. It's been abused for years.
If you need to keep it, then add a `channel:read:chatters` scope; and don't grandfather it in. Sunset.
#TwitchDoBetter
-
Such_a_Moon
commented
It would be nice if this endpoint will also return user IDs, not just their logins. Maybe even chat badges.
-
wopiTV
commented
There is still no official way to get a user list of viewers/chatters. At the moment lots of implementations (especially for activity rewards) rely on undocumented/unofficial endpoints.
I am open for helping out into finding a solution that could work best as a eventsub topic. -
WLG3R
commented
Not only for loyalty, this is very helpful for moderation, so you can see who is in the channel, especially which mods are online or not. The mods are also on the undocumented endpoint.
-
Matt_Thomas
commented
With the scheduled sunset of /NAMES the undocumented endpoint will probably be seeing and increase in usage. I'm sure lots of bot devs would like to see a long term/documented endpoint for chatter lists. Mostly related to loyalty points.
-
moocat
commented
👍 This is still needed even with Twitch's Channel Points