How do I get the authroization id? I can't find that anywhere. I have a client id now but running the example command results in a 401 invalid oauth token

Although I set user:read:email in the requested scope, neither the ID JWT nor the userinfo contains the email claim. What must we do to make this take effect?

The webhook/response for subscriptions returns a payload as

(webhook example)

{

"data": [

    {

        "event_data": {

            "broadcaster_id": "casterID",

            "broadcaster_name": "aCaster",

            "gifter_id": "",

            "gifter_name": "",

            "is_gift": false,

            "plan_name": "Some Subscription ($4.99)",

            "tier": "1000",

            "user_id": "someID",

            "user_name": "someName"

        },

        "event_timestamp": "2020-10-16T17:33:46Z",

        "event_type": "subscriptions.subscribe",

        "id": "1iyAnn4NpVMZ9jYv0HDOQP4SfpS",

        "version": "1.0"

    }

]

}

But it doesn't include information about if it was a 1/3/6/12 whatever subscription or not.

Please extend the payload (for both webhooks and the API) to contain this information about if it's a multimonth purchase

Add a streamline embed option for chat. Be able to remove the header, leaderboard, and footer options to be more inline with the mobile website style.

This comes from an example from the forum, but this would be very helpful on mobile websites, and responsive websites. Having only 1 or 2 lines of chat on screen is counter productive, and a terrible user experience.

https://discuss.dev.twitch.tv/t/possible-to-embed-mobile-ux-of-twitch-chat/28645

For use in internal systems to map to existing IDs they create.

I am confused about this site. Please provide a video and explain more.

https://dev.twitch.tv/docs/authentication

Says

```
Authentication involves:

Registering your app to obtain a client ID and client secret.
Getting a token. This includes specifying scopes, the permissions your app requires.
Sending the token in your API request, to authenticate API requests.

```

But doesn't mention that an Extension is also an Application

This docs fix would be needed on other pages where "registering an app" is mentioned

In a similar fashion as

https://twitch.uservoice.com/forums/310213-developers/suggestions/39228784-extend-clips-api-to-provide-the-mp4-url-so-editors

The Videos API should be extended to provide the (original) VOD to authenticated users where that user is an Editor or better of the channel.

As in unmuted.

For the purpose of backing up/taking a copy of the Twitch stream and/or taking that content (that the streamer owns) for use on other platforms.

Editors can already do this via the Video Dashboard, so the API should support this also

It's as the title suggests.
When I embed a chat and include the parent parameter then that streamer initiates a raid, the chat embed redirects to a standard popout link for the target channel and not the embed link with the same parent as was set. I believe that when we set the parameters they should stay during this process.
eg: twitch.tv/popout/channel/chat when it should be twitch.tv/embed/channel/chat?parent=...

jitendra sah LLGL9RJG2

Add a radio option to extension capabilities, so that if a member of chat is banned, like how chat gets a overlay saying you are banned.

An extension could have a twitch provided blocking overlay for a specific extension if the developer enables this as a option.

So if a member of chat is banned, the extension unloads
And if a chat banned member loads the page the extension doesn't even load and presents the is banned UI (omit the unban request button just overlay the extension)

In a similar fashion to

https://twitch.uservoice.com/forums/310213-developers/suggestions/39910141-copy-subscription-support-for-channel-moderation-s

it would be beneficial to include ban status in the extension JS helper. To save an Frontend->EBS->API round trip to obtain this data.

It would be a boolean unlike substatus which is null/object

Optionally useful to provide data if a active timeout is in place.

A "onBan" callback might be useful (which would only listen to to that users ban status change(s)

https://dev.twitch.tv/docs/extensions/reference#javascript-helper

Change

window.Twitch.ext.onAuthorized(function(auth) {
$.ajax({

url: '/<some backend path>',

type: 'GET',

headers: {

  'x-extension-jwt': auth.token,

}

});
});

to using fetch, or STATE it's a jQuery example

https://dev.twitch.tv/docs/extensions/reference#javascript-helper

Every since refernce to each function is

twitch.ext

This ASSUMES the developer has cast var twitch = window.Twitch somewhere.
It would be more clear if each code reference did

window.Twitch.ext

instead, or mention that twitch is a variable expected to be cast by the developer

There is also some inconsistency where twitch.ext and window.Twitch.ext are used inchangably

https://dev.twitch.tv/docs/extensions/reference#helper-viewer

states for the "twitch.ext.listen" function/callback

Non-Extensions PubSub topics also are supported.

This is no longer true as every non extension pubsub topic requires an Authentication token, and the listen function doesn't provide a way to specify a token.

Or the documentation is unclear on how/which non extension pubsub topics are supported

missing a space on last line