Helix modify channel information endpoint should allow access to editors
The new helix endpoint to modify channel information ( https://dev.twitch.tv/docs/api/reference#modify-channel-information ) doesn't work with a user token from a user that has been added as an editor to the channel. This basicially shuts out any clientside tool used by editors where it's impractical for the broadcaster to directly authorize access. Editors should be trusted enough to be able to choose their own tools.
Allowing access to editors would especially make sense if this is intended as a replacement for the v5 endpoint ( https://dev.twitch.tv/docs/v5/reference/channels#update-channel ), which does allow editors to update the stream title and game. It would also work better together with the replace stream tags helix endpoint ( https://dev.twitch.tv/docs/api/reference#replace-stream-tags ), which also allows editors access.
I would appreciate it if this change could be made to allow tools to continue working when switching to helix.
This is very much needed. I personally want to setup certain commands on my bot that can modify "preset" title/game/tags based on the game im playing/project im working on.
Still no reaction and not planned? It has to be implemented.
This would be very welcome
As twitch forced the move to Helix from V5, I have, too, found out the hard way that channel Editor is no longer allowed to change stream title and game. In my use case this would make it impossible to tell who changed the stream title as everything is now being done by using broadcaster's access token.
To add to this, if an editor prefers a third-party tool (for any number of reasons), then the only way for this to work would be to have the broadcaster grant access to some serverside tool that then uses the broadcaster's token when an authenticated user with access wants to set the title/game. The added complexity of having to handle tokens serverside and having the broadcater grant access when there is no other technical reason for it (for some use-cases that may be required anyway of course) doesn't feel like it adds to security or reliability.
But that aside, having to use the broadcaster token means that the broadcaster's name shows up in the Dashboard's Activity Log for actions that are actually triggered by another user, which seems counterintuitive. This may be unavoidable for some use-cases (e.g. a chat bot allowing mods to change title), but shouldn't be required for use-cases where it makes technical sense to use the editor's token directly (like a clientside tool already using the user's token anyway).
Please consider this. At the moment we have the absurd situation where an editor can change the stream's tags, but not the title/category.
With the impending shutdown of Kraken, we need this. Please fix.