Get moderators endpoint - remove need for broadcaster authorization
The Helix /moderation/moderators endpoint currently requires an OAuth token from the broadcaster. Given you can just do /mods in any chat (not requiring authorization from the broadcaster), what is the point of requiring the authorization here?
I heard the reasoning on the dev stream today for broadcaster tokens. I understand the broadcaster only reasoning now (privacy and control who can pull that list programmatically).
However, I'd ask to allow your channel moderators access to VIPs and mods programmatically as well.
The two new followers endpoints were announced today to "to bring feature parity with first party and third party." It was also mentioned that these will require a moderator scope, which implies that moderators will be able to fetch followers.
If we're talking about feature parity, then removing the broadcaster requirement for VIPs and mods make sense, since anyone can fetch that information first party. However, a good compromise would be to allow moderators access to this information with a moderator-scoped token, same as the upcoming follow endpoints.
I can already do what I need with my use case, as I have the scopes and broadcaster tokens already. However, simply from a feature parity standpoint, it'd make sense to remove the broadcaster token requirement.
That being said, thank you for providing the reasoning behind a broadcaster token.
This is necessary IMO to move away from IRC-based /mods and /vips. It’s a little ridiculous to need a broadcaster token to get that info, when any registered user can simply type /mods or /vips in Twitch chat.
It would be nice if there was an endpoint to get a list of VIPs in channel also, it should work with an app access token too since anyone can use /vips and /mods in chat to get the data.
Edit: Get VIPs exists now but it still requires the broadcaster's token