Shouldn't have a "return values" table at all

The documentation for background color says "Custom background color for the reward" and provides no guidance on the "correct" format for the color (hex code with the # prefix)

When a user purchases multiple giftsubs in one go for a channel.

I saw that Twitch just announced Cooldown options for Channel Points Redemption (https://twitter.com/TwitchSupport/status/1311055756922359808).
It would be very great if this could be added to the API as well

The documentation mentions "a unique ID" that is included with each notification, but doesn't mention the header name.

The page should add documentation for the "Twitch-Notification-Id" header.

The Documentation for the Get Broadcaster Subscriptions Endpoint has a description of Get all of a broadcaster’s subscriptions. - This is ambiguous and sounds like it returns the Subscriptions to other channels a Broadcaster has whereas it returns the users that subscribed to the broadcaster.

I would suggest changing the description to say Get all of a broadcaster’s subscribers. instead.

https://dev.twitch.tv/docs/authentication/getting-tokens-oauth

Both Implicit code flow and authorization code flow label the first step as a "HTTP GET" instead of "this is a link that you need to put on a page for the user you wish to authenticate" or "you need to redirect the user to this page"

Too many people are trying to curl/fetch the URL as the docs seem to label it as a HTTP GET request

The pubsub examples need to be extended for the new multi month gifting

https://discuss.dev.twitch.tv/t/updates-to-pubsub-messages-and-irc-for-multi-month-subscription-gifting/26873

Hello,

Searching in the documentation of the new API I have found these four small errors. They are not at all severe, but they should be remedied in order to facilitate the use of the API.

• https://dev.twitch.tv/docs/api/reference#get-extension-transactions => Link bad rendered in Markdown
• https://dev.twitch.tv/docs/api/reference#get-bits-leaderboard => typo on OAuth Token, missing O
• https://dev.twitch.tv/docs/api/reference#redeem-code => method missing
• https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions => Scope in wrong format (not labeled)

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

user:read:email disappeared and user:edit:broadcast now has the email scope's description.

Similar to

https://twitch.uservoice.com/forums/310213-developers/suggestions/39847792-pubsub-docs-don-t-mention-token-type

All documentation should be revised to describe which kind of token and depending on token type what scopes are needed to call each endpoint.

The documentation for the most part only mentions a scope and doesn't describe what kind of token to use

The scopes page on Authentication(https://dev.twitch.tv/docs/authentication/#scopes)

is missing the documented scope from the Helix Get Moderators

Returns all moderators in a channel.

Authorization
Requires OAuth Scope: moderation:read

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

Unlike other documentation, https://api.twitch.tv/ is omitted from the URL and the example call

The Helix API currently has no way of retrieving a particular users online channels they are following. This is done by the "Get Followed Streams" API in v5 (https://dev.twitch.tv/docs/v5/reference/streams#get-followed-streams)

To get the same behavior in the current Helix endpoints would require TENS of requests each time you wanted to check for the presence of a channel coming online/going offline, instead of the nice single endpoint v5 offers.

I've requested this endpoint for a few years now and was told v5 and Helix will have parity before v5 is officially shutdown, so I hope that's still the case.

You should describe how to work with chat without using an unofficial library that is not owned by Twitch.
At the same time you should explain how to get the Oauth Token not using a website that is also not owned by Twitch but uses "Twitch" in it's name, going against the TOS.

This page should mention that "v5" and the "kraken" api refer to the same thing. Me and my friends always used "Kraken" to refer to this api, it's in the endpoint its self.

I'm sure we are not alone in this, please mention that v5 IS the Kraken endpoint, you should even rename the side-section to say "Legacy Twitch API v5 (Kraken)"

in "HTTPS on localhost: the easy way" part, there is too much of the selection in "We recommend using Google Chrome. In the browser, enable the flag allow insecure localhost. To enable this flag, navigate to: chrome://flags/#allow-insecure-localhost and restarting your browser." sencetnce, for me, "allow insecure localhost. T" is secelted, but i think it should be "allow insecure localhost" only

As we all know that twitch is one of the best platforms for gamers. I want to embed it with my website https://routerinsider.com/best-router-under-150/ so that every person can get benefit from it. How can I embed it?

There's an error in Section "Using cURL to get the information".

curl command needs param -X if you want to specify the method, for example GET in this case:
curl -X GET "<url>"...