Get the authenticated user's emotes (equivalent to existing Kraken endpoint)
This Kraken endpoint provides the emotes a user has access to: https://dev.twitch.tv/docs/v5/reference/users#get-user-emotes
A similar functionality would be nice for the new API as well. It should contain all emotes a user has access to, for example Global Emotes, Subemotes, Bit Emotes, Emotes unlocked by Channel Points and so on (the Kraken endpoint is unfortunately missing some types of emotes).
The emotes returned would be for the authenticated user, with an appropriate scope required.
I am working on an Open-Source Twitch App and this API-Endpoint would be helping us a lot.
Currently devloping an iOS Chat Client and I don't think I can get a fully functional emote menu to work without this endpoint.
To add to this further, please also make sure that the correct set of smilies [ :) :( :/ ] is returned (robot, glitch or monkey), so it's clear which set will actually show up when sent by the user. This also currently appears to be the case with the Kraken endpoint.
@ScottRC While emote-sets tag from `USERSTATE` (and `GLOBALUSERSTATE`) are useful and give us all the information to look up emote sets by IDs I wanted to address the existing issue with that solution here as well - so far, these are the IDs of emotesets I've encountered so far that have the same issue as described by @Rosuav on the Twitchdev forums: `472873131` `477339272` `488737509` `537206155` `564265402` `592920959` `610186276`. Trying to lookup those in Helix returns empty arrays as I believe that whether a user has emotes from those sets or not is tied to user's account.
The only alternative would be to use Kraken's Get (Authenticated) User's Emotes, but given today's announcement about Kraken decomission we'd need a way to query those in Helix. Many third-party chat clients (including the one I currently maintain) use this functionality and it's very important to us.
To add to this, to get the most usefulness out of this it would be nice if the reponse would contain the following information for each emote:
* Name (what you would type in chat)
* Type (sub/bits etc.)
* Channel id, channel name (Including the name, not just the id, means fewer API requests to get the name if it's required for something)
* Set id
* Animated (yes/no)
To add to this, the IRC USERSTATE emote-sets tag, should also include the new emote set ID's. The documentation doesn't seem to give devs any information that it excludes bit emotes etc. https://twitch.uservoice.com/forums/310213-developers/suggestions/43663572-irc-userstate-emote-sets-should-include-bit-emotes