160 results found
-
Change description of broadcaster_id in create clip 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.
3 votes -
Wording on refreshing a token is confusing 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
3 votesExpanded upon in new documentation: https://dev.twitch.tv/docs/authentication/refresh-tokens/
-
Helper: viewer is misleading as the viewer object is populated on all views not just the channel page 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
viewerhelper object exists on all views!3 votes -
Get Broadcaster Subscriptions docs example incomplete 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.
3 votes -
Extension popout "by default" From: https://github.com/twitchdev/issues/issues/72
Brief description
By default, pop-out control is enabled for panel Extensions and for extension “live configuration views” (see the Live Config Path setting on the Asset Hosting tab in the Extensions manager).
https://dev.twitch.tv/docs/extensions/required-technical-background
The documentation suggests that extension developers can disable pop-outs. Which is not the case
3 votes -
User/Channel ID needs to be a string From: https://github.com/twitchdev/issues/issues/70
Brief description
The documentation for creating signing JWT's don't explicitly state that
user_id/channel_idin JWT's need to be an explicit string literalhttps://dev.twitch.tv/docs/extensions/building/#signing-the-jwt
https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-messageExpected documentation
Where: exp is the Unix epoch timestamp when the payload will expire. Be sure to provide a buffer, to allow potential positive time drift. user_id is the Twitch user ID that owns the extension, where the user ID is cast as a string literal. role is set to external.3 votes -
Extension viewer Session Token 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.3 votesCorrected for today’s deployment
-
Get Broadcaster Subscriptions with an App Access Token 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
3 votesAdded to today’s documentation deployment
-
Config Service links to wrong reference 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/referencebut the configuration API is documentedhttps://dev.twitch.tv/docs/extensions/reference#set-extension-required-configuration3 votes -
onPositionChanged still in docs From: https://github.com/twitchdev/issues/issues/36
Brief description
https://dev.twitch.tv/docs/extensions/reference#helper-extensions
The JS helper/callback function
onPositionChangedis still documented but is no longer relevant post video component redesignExpected documentation
Section Should be removed
3 votes -
Locales/language valid options 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
languagequery 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
3 votes -
Confusing scopes in IRC Documentation On the IRC Concepts page (https://dev.twitch.tv/docs/chat/irc)
it says: ", you must authenticate with Twitch and get a User Access Token with chat:read (to read chat messages over IRC) and chat:write (to send chat messages over IRC) scopes."but the page about scopes (https://dev.twitch.tv/docs/authentication/scopes/#irc-chat-scopes) never mentions a "chat:read" scope.
I assume this is meant to say "chat:edit"?2 votes -
Typo on Channel Ad Break Begin Condition The "Channel Ad Break Begin Condition" has a typo - it currently says "broadcaster _ id" but should be "broadcaster _ user _ id"
2 votes -
[Typo] type exists for Channel Points Automatic Reward Redemption Add Event reward.message reward.message
should use Message type defined:
https://dev.twitch.tv/docs/eventsub/eventsub-reference/#message2 votes -
[Typo] duplicate Channel Moderate Event raid.user_name https://dev.twitch.tv/docs/eventsub/eventsub-reference/#channel-moderate-event
raid.user_name is repeated twice
2 votes -
[Typo] incorrect definition Channel Chat Notification Event resub.is_prime https://dev.twitch.tv/docs/eventsub/eventsub-reference/#channel-chat-notification-event
Channel Chat Notification Event type
resub.is_prime has incorrect description2 votes -
[typo] channel.chat.user_message_hold Authorization https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelchatuser_message_hold
in Authorization section word scope is outlined along the actual scope2 votes -
Clips API documentation change The hyperlink in the sentence: "To create a clip from a broadcaster’s stream, use the Create Clip API" points to:
https://dev.twitch.tv/docs/api/reference/#get-clips
When it should probably point to:
https://dev.twitch.tv/docs/api/reference/#create-clip
As it relates to creating a clip.
2 votes -
I'd love to reach out to someone just to ask a simple question or two! Discord Server or something please! Make a Discord server for this please!!
2 votes -
'Get Stream Key' Doc URL is missing Request Method The URL for endpoint "Get Stream Key" is missing the "GET" request Method in the reference documentation. This is the only endpoint with this issue.
https://dev.twitch.tv/docs/api/reference/#get-stream-key2 votes
- Don't see your idea?