On the new Helix endpoint, https://dev.twitch.tv/docs/api/reference/#get-extension-transactions and therefor https://dev.twitch.tv/docs/api/webhooks-reference/#topic-extension-transaction-created the signed receipt that comes with onTransactionComplete from the JS Helper is missing. In order to audit and avoid man in the middle attacks, a signed JWT that can only be verified with the client secret should be sent on all endpoints sending monetary transaction data.

r9k mode
follower mode
subscriber mode
emote mode
slow mode

See https://blog.twitch.tv/channel-moderation-tools-in-chat-4188af21dbf9 for details.

Currently the management of extension SKU's is only done via the Developer Rig.

Since the rig is an optional, many people are developing / testing without using it & the fact that its a development environment, its a strange place to place/manage production SKU's. These would be better managed from the platform itself under the Monetization tab of each Extension.

Allowing developers to roll back a released version to another (approved) version would allow developers to quickly address breaking issues without going through a review process.

The current Helix endpoint doesn't give the broadcast ID, so there's no way to grab which broadcast the VoD is from.

Similar to the Bits Leaderboard, please add a gifted subs leaderboard API, so we can see everyone who has gifted a sub in the channel.

I would like to work with embeds, and more specifically a way to get how much the current player's stream latency is. From what I can tell, player.getPlaybackStats() was the only way to do this, and is now deprecated, and returns null 99.99% of the time. (I was lucky to get it working once, but yeah, it's gone.)

Include the displayName in the javascript helper without asking any special permision or without doing any special function (like using bits).
This value it's only available if the user send bits and the transaction get complete.

Currently, I find the docs hard to get through, although most documentation is there. It would be nice if you can go to the part of the docs that you might need, at the moment you are having a choice. For example when choosing what type of extension you want, that it will have a link to that specific documentation. Let's say you have chosen Panel, you then get a link to a/some of the example repositories for a Panel, the test channel, and a link to the documentation for creating a Panel.

Now it is not possible to get the number of streams in a certain section without sending a large number of requests to the API.

Adding the commonly-used game title field to the Get Streams endpoint payload (similar to the addition of user name) will allow developers to make less calls for the data needed. In other words, Get Games would not need to be called for every game id to get one more field.

Moderators are able to add a reason/description whenever they ban people in chat (/ban [username] reason)

This information is currently only available in the "not allowed to use" GraphQL-api, but should also be added to the documentet endpoints; /moderation/banned and /moderation/banned/events

(Ban-reason is different from moderator-comments.)

Being able to order some of the Helix endpoints by date would be useful

Follower for example would need in some cases 11k+ calls to the follower endpoint to just get the 100 followers who had followed for the longest time.

This would also be good in the subscription endpoint if cumulative and streak get put into the Helix API