Helix endpoint to get supported formats and template for a given emote ID?

[BarryCarlyon]

I tend to always use

default - then its aniamted if it is and static if it isn’t
2.0 for size - what size you want to use will depend on your app and it’s scaling and if you want retina display/etc and so on
dark/light twill depends on the user using my chat app and let them theme selete, but generally I use dark as my default

so, this is from a live thing:

'<img class="emote" src="https://static-cdn.jtvnw.net/emoticons/v2/' + emoteID + '/default/dark/1.0" />', 

To quote the docs

The format of the image to get. For example, a static PNG or animated GIF. Use default if you want the server to return an animated GIF if it exists, otherwise, a static PNG.

Default makes life easier as you don’t need to know what formats a given emote supports.

Generally speaking all emotes have a 1.0/2.0/3.0 so you don’t need to worry about that.

So there is a happy default you can use to construct URL’s with.

@outadoc

The emotes documentation insists quite a lot that one should not be trying to guess the supported scales, themes, and formats for a given emote, but instead use the helix/chat/emotes/set route to get more info about the emote and use the returned info and template URL to craft the emote’s image URL.

The logic here is that you are operating on a single channel set of emote, not all emotes across all of Twitch, it would seem. So you generally only need to fetch one set of emotes, or only the emotesets the authenticated user has access to.