# New chatters endpoint **URL:** \ **Category:** API\ **Created:** [April 22, 2023, 10:56pm UTC](https://staging-discuss.dev.twitch.com/t/new-chatters-endpoint/45300 "2023-04-22T22:56:22Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Travis\_Miller](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/travis_miller/32/7007_2.png) [@Travis\_Miller](https://staging-discuss.dev.twitch.com/u/Travis_Miller)\ **Post date:** [April 22, 2023, 10:56pm UTC](https://staging-discuss.dev.twitch.com/t/new-chatters-endpoint/45300/1 "2023-04-22T22:56:22Z")
Hi! the endpoint: [https://api.twitch.tv/helix/chat/chatters](https://api.twitch.tv/helix/chat/chatters) seems to be extremely slow at recognizing new people joining chat, and slow at removing them from the list when they leave. IIRC the old endpoint was far superior although it was undocumented. I’ve had a few people complain to me about not detecting viewers in chat. example: [https://api.twitch.tv/helix/chat/chatters?first=1000&broadcaster\_id=73101896&moderator\_id=73101896](https://api.twitch.tv/helix/chat/chatters?first=1000&broadcaster_id=73101896&moderator_id=73101896) Is there any way to improve the timing and accuracy? ---
**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\ **Post date:** [April 22, 2023, 11:20pm UTC](https://staging-discuss.dev.twitch.com/t/new-chatters-endpoint/45300/2 "2023-04-22T23:20:16Z")
In my experience it seems fine to me. > [@Travis\_Miller](#): > > seems to be extremely slow at recognizing new people joining chat A spot test I showed up in a channel on the 3rd check, where I’m checking every minute. Seems speedy enough to me/in line with helix operations. > [@Travis\_Miller](#): > > I’ve had a few people complain to me about not detecting viewers in chat. > exampl after migrating to the new endpoint I’ve fielded no reports on for this across a handful of channels that I operate usage of this endpoint (usually for the purpose of currency systems) ---
**Author:** ![DevMcGee](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@DevMcGee](https://staging-discuss.dev.twitch.com/u/DevMcGee)\ **Post date:** [April 23, 2023, 4:11pm UTC](https://staging-discuss.dev.twitch.com/t/new-chatters-endpoint/45300/3 "2023-04-23T16:11:33Z")
So your testing was that it took 3 minutes, but that seems speedy enough to you. Surely you can understand that 3 minutes is unacceptably slow for various use cases? So saying it seems fine to you is kind of silly. _Why would you ever need to do something that isn’t exactly my use case?_ > [@Travis\_Miller](#): > > Is there any way to improve the timing and accuracy? Not if Twitch doesn’t fix it, but I think it’s far more likely that things will continue to get worse, rather than better. ---
**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\ **Post date:** [April 23, 2023, 4:29pm UTC](https://staging-discuss.dev.twitch.com/t/new-chatters-endpoint/45300/4 "2023-04-23T16:29:49Z")
> [@DevMcGee](#): > > So your testing was that it took 3 minutes, but that seems speedy enough to you. Surely you can understand that 3 minutes is unacceptably slow for various use cases? So saying it seems fine to you is kind of silly. User didn’t describe the speed they were getting to quntify why it wasn’t acceptable to them. They just stated it was _slow_ and didn’t describe why. And off hand I don’t recal if the old endpoint was quicker than what helix is, but I suspect it was around about the same time wise. Additionally I suspect the _new_ endpoint relies on the same internal service as the _old_ endpoint, so there shouldn’t be a difference in quality/speed. So in summary: I shared the times I observed, to compare to what OP observed (which they didn’t state what they observed) _and_ shared this forum post in the TwitchDev Developer Discord to seek other opinions. So what is `extremely slow` defined as? ---
**Author:** ![Dist](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dist/32/7192_2.png) [@Dist](https://staging-discuss.dev.twitch.com/u/Dist)\ **Post date:** [April 23, 2023, 4:38pm UTC](https://staging-discuss.dev.twitch.com/t/new-chatters-endpoint/45300/5 "2023-04-23T16:38:43Z")
> [@DevMcGee](#): > > Surely you can understand that 3 minutes is unacceptably slow for various use cases? If you need more responsive data, perhaps create a UserVoice with your use case for needing the data faster than has always been available, as even the previous endpoint has slow responsiveness and varied greatly so 3 minutes is about par for the course for this data. ---
**Author:** ![DevMcGee](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@DevMcGee](https://staging-discuss.dev.twitch.com/u/DevMcGee)\ **Post date:** [April 24, 2023, 12:37am UTC](https://staging-discuss.dev.twitch.com/t/new-chatters-endpoint/45300/6 "2023-04-24T00:37:48Z")
IIRC, the old endpoint would typically show a new user within 30 seconds but it varied a lot and wasn’t reliable. > [@BarryCarlyon](#): > > Additionally I suspect the _new_ endpoint relies on the same internal service as the _old_ endpoint, so there shouldn’t be a difference in quality/speed. I suspect you are right about it being internally the same data, so I suspect it is no more reliable. But there are various reasons why update latency could change, such as changes to the caching. > [@BarryCarlyon](#): > > They just stated it was _slow_ and didn’t describe why. > [@BarryCarlyon](#): > > So what is `extremely slow` defined as? _mu_. Even if you are asking rhetorically, that hints at a major misunderstanding. I hope this is perfectly clear: “slow” and “speedy enough” are **subjective** : they vary from case to case. That is why responding “[3 minutes] seems fine to me” is unhelpful. > [@Dist](#): > > If you need more responsive data, perhaps create a UserVoice with your use case for needing the data faster than has always been available, as even the previous endpoint has slow responsiveness and varied greatly so 3 minutes is about par for the course for this data. Not really, but it’s moot anyway. Twitch has ignored requests for more accurate and timely information for years and has been making what is available less useful. They do not care about others’ use cases. ---
**Author:** ![matwalsh](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/matwalsh/32/7201_2.png) [@matwalsh](https://staging-discuss.dev.twitch.com/u/matwalsh)\ **Post date:** [April 24, 2023, 3:54pm UTC](https://staging-discuss.dev.twitch.com/t/new-chatters-endpoint/45300/7 "2023-04-24T15:54:05Z")
> IIRC the old endpoint was far superior although it was undocumented. They use the same datasource; there should be no difference in update speed. ---
**Author:** ![system](https://d2spem0quai2ol.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://staging-discuss.dev.twitch.com/u/system)\ **Post date:** [May 24, 2023, 3:55pm UTC](https://staging-discuss.dev.twitch.com/t/new-chatters-endpoint/45300/8 "2023-05-24T15:55:04Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.