Add subscriptionStatus to extension JWT. Currently subscriptionStatus is in Twitch.ext.viewer. With it in the JWT, it can be verified by an extension backend.

We would like subs tenure in Helix in order to use this for merch extensions providing tenure-based merch options.

For /moderation/banned and /moderation/banned/events.

It would be convenient to have the ability to query Bits transactions based on broadcaster id and user id. This is extremely helpful for Extensions with lots of transactions and saves on calls to the API that would be necessary for paginating until the desired transaction is found.

Partners get a verified badge, it would be nice for published developers to get a badge too, maybe after a certain usage requirement of their extension, like how partners have to hit certain limits to become partner, maybe enough usages or page views of the extension will get a dev a badge.

Currently we have to grab this Informtion about autohosts from the IRC Chat. But why? Why not just adding a boolean (for example: "isAutohost": true/false) into the already existing hosts endpoint for tmi.twitch.tv o.O?

Would love to have something like that. Thanks!

Right now there is no official way (there is an undocumented endpoint) to determine whether a stream is sub only or not. Subscriber only status prohibits a lot of people from interacting with the stream, so it'd make sense for applications to be aware of such a state.

A user's created timestamp is not yet available through Helix. The updated timestamp is personally less useful but would be nice for consideration.

I'm looking to add functionality to an extension where all bits count but bits within the extension have a weighting against those that aren't. I have my own bits transactions through the transactions endpoint but at the moment I have to ask for the scope separately. As my extension is already asking for the `channel:read:subscriptions` I thought it may be a good option to add this as an extra scope to ask for or possibly ask for within the same auth loop as the subscription read

Some third-party developers request id access on their Extensions just for the purpose of getting a viewer's username to build a more personalized experience. The only way to do so is by relying on the Helix user endpoint on their EBS. The Helix team already modified any payload that has a user id to also deliver a username and save developers the extra step of using the /users endpoint, so it's natural for Extensions to follow that path.

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.

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

The given JWT representing the transatction receipt contains a time field that is stringified version of the Golang time object. Parsing in this format is significantly harder than a ISO standard format.

When a VOD gets deleted, there's no known way to retrieve the time of when the clipped event occurred live. Knowing the time of the event helps tremendously when creating highlights for an individual as it allows chronological ordering with no errors, whereas if one uses the _created_at_ key from the **Get Clip** api endpoint, you're subject to the time when the clip was created.

This topic was discussed briefly on the twitch developers forum, https://discuss.dev.twitch.tv/t/clip-event-timestamp/19441/3 .

Get Streams does not denote if the stream is mature or not.