The Kraken API for querying videos lists the available resolutions for archived broadcasts and current streams. The new API does not.

https://dev.twitch.tv/docs/api/reference#get-videos

I would like to see more than one user per schedule API query. Similar to querying the streams and channel information from up to 100 users. That would be of great help with the rate limits.

Best greetings ^^

When creating a Drop, it would be great if you could set it up to give the viewer an option to choose "x" number of Rewards from a pool of "y" options.

Examples:

1. The viewer is presented with the options of an Ultimate Ball, a Super Ball, or a Mega Ball as their Reward, and they're allowed to pick one.

2. The viewer can choose two items from the following: coins, a skin, a beta-access key.

For example when I request emote set 300548756 (The rpg limited time emotes) It only returns RPGAyaya when I as a user possess all of that emote set. other limited time sets do the same with some not returning any emotes at all.

Where's the link to the tutorial?

The example curl request here:
https://dev.twitch.tv/docs/api/reference#check-automod-status
Doesn't work.

1) It needs a broadcasterid query param
2) It needs the content-type header (application/json)
3) I get a 500 error using the provided "userid"s in the post body, using other user_ids works

I spent more time than I care to admit figuring this out, so it seems like fixing this will probably hep somebody out in the future.

If these three things are fixed the call succeeds.

So I'm trying to do a multi-room audio solution with Mopidy (https://mopidy.com/) and Snapcast (https://mjaggard.github.io/snapcast/), and I'm following many DJs on Twitch, and tune in for the music. I'd like to be able to have a Mopidy extension to be able to receive and listen to Twitch streams from the server, without having to use my phone or anything.

I don't mind if I need to login/OAuth token, I don't mind for the usual occasional audio ads, I just want to be able to access the AUDIO stream so I can listen to it more conveniently.

Limits like max length for transport.secret property would be good.

In the subscription fields definition, both cumulativemonths and streakmonths are listed as strings when they are very clearly integers.

Further, it would help greatly with readability if the fields were listed in the order they appear in the supplied JSON snippets.

The Predictions documentation has incorrect information listed for how the Top Predictors are defined. The documentation says the list contains a two-level class called "user" and all properties are below that (EX: "user.id"). However in reality, there is just one class that contains all the information and the "user" part is appended in front of a few relevant properties (EX: "user_id"). Screenshot below for comparision:

https://imgur.com/a/yNXa2G8

It was very useful for my little game but I would have liked a vip tag.
Except that it has served me perfectly. Thank you very much.

There does not seem be an equivalent for v5's chat endpoints. In particular, there does not appear to be an endpoint for getting all emoticons such as https://api.twitch.tv/kraken/chat/emoticons.

Include the same data as received from https://api.twitch.tv/helix/moderation/banned/events. Primarily event timestamp (time when the ban/unban action occurred) and the id (allows checking for duplication with eventsub messages already received when pulling from helix)

Add the following fields to "event" paylod for ban/unban eventsub messages:
"id": "1IPFqmlu9W2q4mXXjULyM8zX0rb",
"action_timestamp": "2019-03-13T15:55:19Z"

EventSub Beta for channel.prediction.end event/status should be consistent with helix casing of status, i.e "Valid values are RESOLVED, and CANCELED."

EventSub Beta for channel.poll.end and channel.poll.progress event/status should be consistent with helix casing of status, i.e "Valid values are COMPLETED, ARCHIVED, and TERMINATED"

The current APIs max out at 100 items per page, and while this is fine for most channels, there are some where you end up having to paginate for a long time to reach the end of the list.

Given there is rate limiting in place, would it be possible to make an endpoint (or use the current endpoints and add an "all" query parameter) with a high rate-limit cost that allows for the bulk fetching of this information?

Can you please double check the meaning of the sentences covered in this page (ex: Send the user you want to authenticate to your registered redirect URI. -> you dont't send them to the redirect URI but to the Twitch uri under the cited pharagraph) And the 'token+idtoken' is not equal to 'token%20idtoken' (the 'token id_token' is) the '+' signs encoded to '%2B' which trows an error whereas the ' ' (space) encoded to '%20' which returns the desired result.