The hub.secret property needs far more explaining of how the secret is generated:

"The X-Hub-Signature header is generated by sha256(secret, notification_bytes)"

It should say something along the lines of

"The X-Hub-Signature header is generated by using HMAC sha256 with the provided secret being the one specified in hub.secret: hmac(sha256, hubsecret).hash(notificationbody)"

Unhelpful page. I want to send an API request to test through Postman, but I do not understand what format to put it in. It is asking for an OAuth token, but that request does not mention anything about that. Very confusing.

the V5 scope 'user_read' is not listed here. In the migration document it suggests that that is equivalent to the helix scope user:read:email. Is that correct?

Is there a V5 scope that matches the new helix user:read:broadcast

https://imgur.com/a/kBcNDeh

The use of bullet points reads and the "and" tacked onto the end of the first bullet point makes it unclear

The wording should be revised so it's more obvious that "onTransactionComplete" is to be sent to instances where the userID matches the userID that initiated.

Since the first bullet point is superflous, since the userID of the first bullet point is also matched by the second bullet point.

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

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

SNIPPET STARTS

onChanged
Twitch.ext.viewer.onChanged: void function(callback: Function())

This function binds a callback will be invoked when the viewer’s status changes (e.g. if a viewer subscribes and changes their subscription status).

SNIPPET ENDS

Cannot tell if broken or only triggers on subscription status change.

IE is it supposed to trigger on role changes? If so it's bugged, if not the documentation needs to document what does cause onChanged to be called

Pagination Support
None.
There is a limit of only 50 Custom Rewards on a channel at a time.

It's unclear if that means 50 active rewards or 50 total rewards. It should be more plain text/clear.

The help article

https://help.twitch.tv/s/article/making-the-most-of-channel-points?language=en_US

doesn't mentioned this limit either.

This is out of date. Update it please.

It appears that the Glitch file has been changed! I couldn't get the !dice command to work, until i figured that the command had been changed to !d20 along with the number of sides changed to 20. Or maybe this was a ploy.... to help me understand coding better... Thanks!

The example and/or documentation of the "Channel Points Event Message" seem to be wrong/misleading, because the example reply does not match the structure of "Message Parameters: All Messages"

https://dev.twitch.tv/docs/api/reference#modify-channel-information

The example calls uses JSON, but the documentation talks about Query String/URL encoded form.

Docs should cover both possibilities and examples should cover both methods

https://dev.twitch.tv/docs/embed/ and it's child pages mention the requirements for parent but never SSL

Extensions Manager Overview -> Capabilities -> Request Identity Link

Description refers to viewer as a male ('his'). This is likely to offend some people?

The description of the broadcaster_id inside of the Create Clip endpoint is very confusing because it states that this is the id of the stream but it really is the id of the broadcaster as the name suggests.

https://dev.twitch.tv/docs/authentication#refreshing-access-tokens

"
How to Refresh
To refresh a token, you need an access token/refresh token pair coming from a body. For example:
"

You need only the "refresh token" and "client secret"

You can lose the access token, and still get a new token if you have a refresh_token

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

The Twitch.ext.viewer object is a collection of info about the twitch viewer that is watching the channel page where your extension is activated. It will only be populated if the viewer is logged in, and only after the `onAuthorized` callback has been called. Accessing its properties will otherwise return `null`.

Should be

The Twitch.ext.viewer object is a collection of info about the twitch user that is watching the extension view.

Or something, as the viewer helper object exists on all views!

The Get Broadcast Subscriptions docs https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions was updated to include gifterid and giftername fields, but neither of these were added to the example.

Also, the example is erroneous because it shows the same user id for both broadcaster and subscriber, but they represent different usernames, which is impossible.

https://dev.twitch.tv/docs/authentication/getting-tokens-oauth#oauth-client-credentials-flow

There's no information about error response and it doesn't seem to be fully compatible with RFC 6749 which means I can't find info about possible errors easily.

From: https://github.com/twitchdev/issues/issues/56

Brief description

Documentation describes that there are functions such as followChannel and requestIdShare but the documentation doesn't mention that these functions don't work in the rig (at time of writing)

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

Additional context or questions

https://discordapp.com/channels/504015559252377601/523676096277905419/676767529666084864