The recent announcement "Updates to PubSub Messages and IRC for Multi-Month Subscription Gifting" (https://discuss.dev.twitch.tv/t/updates-to-pubsub-messages-and-irc-for-multi-month-subscription-gifting/26873) and IRC Tags docs (https://dev.twitch.tv/docs/irc/tags#usernotice-twitch-tags) lists the new "msg-params-gift-months" tag, but like all other so far it's actually singular "param" not "params" ("msg-param-gift-months") in reality.

The Helix Users endpoint docs state the "user:read:email" scope as required, although it is an optional scope if you also need the users email returned.

On the extensions/manager dashboard page

The options on the "Activated" extensions bottom right is configure and uninstall

Streamers are more likely to uninstall than deactivate as the trashcan/uninstall is too prominent compared to deactivate from slot, for if a streamer wants to deactivate instead.

The uninstall dialog doesn't mention deactivate either, "you are about to uninstall are you sure you don't want to deactivate instead"?

As per

https://discuss.dev.twitch.tv/t/requiring-oauth-for-helix-twitch-api-endpoints/23916

None of the documentation is updated to reflect this change.

Yes it's not required yet. But it's good practice for new developers to be using the new oAuth procedure now

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

Omits

• channel:read:redemptions

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

Brief description

https://dev.twitch.tv/docs/api/webhooks-guide

Limits: By default, each client ID can have at most 10,000 subscriptions. Also, you can subscribe to the same topic at most 3 times.

Seems to be ambiguous to a lot of developers, they seem to think the that "3 times" means they can renew it 3 times then they are SOOL

Expected documentation

Limits: Each client ID can have at most 10,000 subscriptions. Where you can have 3 active subscriptions to a topic at the same time. Where an active subscription is defined as a topic/callback pair.

All of the new emote and badge endpoints can be accessed using an App Access Token except for /chat/badges which needs a User OAuth Token.
I don't see why this endpoint needs a user token since the badges can be viewed publicly on the subs page and It doesn't reveal any private info about a user.

The "GET helix/search/channels" endpoint only gives the game_id and not the game title, this would mean extra API calls that could be avoided if you included the game name in the response.

Title

There should be a field to indicate the owner "clientID" or a "mine: true/false" to represent if the rewards returned by "Get Custom Rewards" belong to the calling clientID or not.

OR

add an optional query string parameter

| name | required | type | description
| -------------------------------------------------------
| mine | no | boolean | if true only return rewards created by this developer/ClientID

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

Brief description

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

documentation wrong:

sessionToken
Twitch.ext.viewer.isLinked: string

The encoded JWT. This is the same as the token property of the authData parameter that currently gets passed to the onAuthorized callback.

Expected documentation

sessionToken
Twitch.ext.viewer.sessionToken: string

The encoded JWT. This is the same as the token property of the authData parameter that currently gets passed to the onAuthorized callback.

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

Brief description

Get Broadcaster Subscriptions doesn't describe how you can use an "App Access Token" for an extension that has sub status enabled, to use the end point

Expected documentation

Describe that an "Extension App Access token" can be used when a broadcaster has granted the "channel:read:subscriptions" scope via the Twitch Extension Manager

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

Brief description

https://dev.twitch.tv/docs/extensions/building/#using-the-configuration-service

Mentions "twitch api reference" but the config service endpoints are on in the Extension Reference

For extension examples that leverage the configuration service see the new Twitch API Reference. Also, see these repositories:

Expected documentation

Links to https://dev.twitch.tv/docs/api/reference but the configuration API is documented https://dev.twitch.tv/docs/extensions/reference#set-extension-required-configuration

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

Brief description

The documentation doesn't advise anything regarding what languages/localses exist/are valid to be called.

For example

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

has a language query string argument, but doesn't advise what is valid for a langauge.

Expected documentation

Document the list of locales of if it matches a ISO, update documentation on endpoints using language/locale with a note about what is valid

Additional context or questions

Raised/queried on discord

https://discordapp.com/channels/504015559252377601/523675960797691915/664243349309620225

Allow developers to sign up for a specific time slot where they can rely on an extension reviewer to review the extension.

example doesn't work "error":"Unauthorized","status":401,"message":"OAuth token is missing"}curl: (3) URL using bad/illegal format or missing URL

Hola equipo de Twitch Api, me preguntaba si hay una forma de SEGUIR a un canal en especifico usando la API?, después de terminar el flujo de OAuth y obtener el token de acceso.

Channel Update Notification Example states both user_id and user_name are returned, when actually it returns broadcaster_user_id and broadcaster_user_name

Ref: https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types#channelupdate