Give developers access to GQL and the full suite of actions.
I'm aware that this is a duplicate but I feel that the answers given have been unsatisaftory, GQL is a well-known and understood standard, hence the tmi.js API would not be needed anymore, nor would other twitch-specific packages. There is no reason not to give access to this given that we all know that it's in use internally and that the security requirements would be no different.
I think that enabling this and managing it safely would be far more secure than it remaining undocumented as developers will use the GQL endpoints no matter how much their use is discouraged as we want to push the platform further and integrate deeper into Twitch, increasing our investment, and that of streamers.
It would also reduce work for the Twitch dev team as there will only be one API to maintain, test and keep up to date and as stated before there would be no need for specific twitch clients (either twitch-maintained or community-maintained.)
-
We understand that there is functionality in the first-party GQL interface that could be useful for third-party development, but we are not considering third-party access or a dedicated third-party GQL interface at this time.
Twitch's current priority is to update and improve Helix endpoints to be the one, singular API. There is considerable work to be done in this space before we consider adding other interfaces. GQL is functionality we may consider in the future, but we want to strengthen a foundation first.
This ticket will be closed since GQL is not on the roadmap and we want to be transparent about that rather than leaving the suggestion open. However, trust that it is evaluated often, and we would consider an RFC or beta program to make sure we get it right working with the community if and when it makes sense to include.