76 results found
-
Add existing IRC WHISPER command to IRC documentation The IRC gateway passes whispers using the WHISPER code:
[16:36:15] [@] @badges=bits-charity/1;color=#3E2E18;display-name=foo;emotes=;message-id=2;thread-id=21001676_470220570;turbo=0;user-id=2109996;user-type= :foo!foo!foo.twitch.tv WHISPER myuser :this is a whisperBut I am unable to find any reference to that code on https://dev.twitch.tv/docs/irc/commands where I would expect it, or any other documentation page under the "Chatbots and IRC" section.
I would suggest adding the WHISPER command to the list of commands at the top of the page on the IRC: Commands section, something similar to:
WHISPER Receive a Whisper message from another user
and then the prototype at the bottom, to include the fact that it appears the WHISPER command is…
15 votesReceiving whispers is no longer available in IRC and instead should be handled by the user.whisper.message EventSub event.
-
Extension Pubsub Docs missing whisper targer. https://dev.twitch.tv/docs/extensions/reference/#send-extension-pubsub-message
The docs say Valid values: "broadcast", "global".
But, the target 'whisper-opaqueId' to send "per user" pusub message is missing.
14 votesPubSub was decommissioned on April 14, 2025, and no new features are planned for it.
-
PubSub Docs don't mention Token Type From: https://github.com/twitchdev/issues/issues/25
Brief description
https://dev.twitch.tv/docs/pubsub#topics
PubSub documentation mentions the requirement to use an oAuth token, but doesn't directly specify which type of token, nor the requirement for the UserID of the token to match the UserID of the topic.
Authentication All topics require an OAuth token, but only some topics have a specific required scope (noted in the table below). Available Topics All topics require an OAuth token, but only some topics have a specific required scope (noted in the table).Expected documentation
…Authentication All topics require a User Access OAuth token, where the UserID of the token matches the10 votesPubSub was decommissioned on April 14, 2025, and no new features are planned for it.
-
Accurate documentation All of your tutorials, links, and/or instructions are dated and unhelpful.
Try having someone follow any of this step-by-step, from scratch, and see if they can get something working, because I, nor my partners can make any usable sense of what is presented about extensions and creating/testing them.
8 votes -
Get Broadcaster Subscriptions Events From: https://github.com/twitchdev/issues/issues/8
Brief description
The subscription events API is documented as a Webhook topic. but not as a API Endpointhttps://dev.twitch.tv/docs/api/webhooks-reference#topic-subscription-events
It used to be in the documentation but is missing
Expected documentation
https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptionsBut for
https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions-events8 votesNow available in EventSub instead: https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelsubscribe
-
Data Retention for Banned Events and Moderator Events Both
https://dev.twitch.tv/docs/api/reference#get-banned-events
https://dev.twitch.tv/docs/api/reference#get-moderator-events
Only hold only "data" for a finite time period.
The documentation does not note the time period that data is retained and returned for.
Hypetrains does not it's 5 days.
7 votesThese APIs have since been deprecated
-
PubSub Topics: no moderator topic examples/documentation https://dev.twitch.tv/docs/pubsub
Has no examples or documentation for payloads for chatmoderatoractions
7 votesPubSub was decommissioned on April 14, 2025, and no new features are planned for it.
-
Fix TMI JS example with Promise handling https://dev.twitch.tv/docs/irc#overview
Row:
client.connect();Should be replaced with:
client.connect().catch((err) => {console.log('Connection error!', err)});
or smth like that.Let's show users how to write good code, and show them, that all Promises should be handled. Unhandled promise rejections is bad!
Tmi.js Library also have connect example which contain promise handling
7 votes -
msg-id tags page outdated/incorrect From: https://github.com/twitchdev/issues/issues/68
Docs location: https://dev.twitch.tv/docs/irc/msg-id
bad_ban_global_mod&bad_timeout_global_modare gone for as far as i know (ref: https://blog.twitch.tv/en/2018/12/13/thank-you-global-moderators-4d44cfccf22/)Missing notices for vip events (
vip_success,unvip_success,no_vips,bad_vip_grantee_banned,bad_vip_grantee_already_vip,usage_vip&bad_unvip_grantee_not_vipMight have missed some.First line says "These tags apply to both the" and than only names one thing.
usage_untimeout has "/raid <username>" in the message.
7 votesThese IRC tags have since been deprecated
-
Webhooks topic(s) don't note required oAuth From: https://github.com/twitchdev/issues/issues/59
Brief description
Mod Change and Channel ban Change events don't note the required oAuth scope needed for the topic
https://dev.twitch.tv/docs/api/webhooks-reference#topic-moderator-change-events
https://dev.twitch.tv/docs/api/webhooks-reference#topic-channel-ban-change-eventsExpected documentation
Add, (similar to
Topic: User Changed)Authentication User Access Token must have the `moderation:read` for the user in questionAdditional context or questions
6 votesWebsub has since been deprecated in favor of EventSub
-
Please add an example payload of a resubgift/anonresubgift to the PubSub docs I raised https://twitch.uservoice.com/forums/310213-developers/suggestions/41016568-context-resubgift-in-resub-events?tracking_code=8f96eb083a992136c313fb0ca1d79054 because I ctrl+f'ed for context as apposed to ctrl+f-ing for resubgift.
Please add an example for a resub/anonresubgift
5 votesPubSub was decommissioned on April 14, 2025, and no new features are planned for it.
-
Authentication Docs Improvement Honestly this whole documentation is a bit sloppy. There should be clearer examples of using the APIs as I had to go Googling how the authentication actually works as the headers seem to be different than this suggests.
4 votesThe documentation has since been updated for clarity
-
Inaccurate info in instrcutions 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!
4 votesThe Glitch example has since been removed
-
Chat and Pubsub - channel:moderate As per this other uservoice
The moderation actions PubSub at time of writing requires a key from the channel you wish to listen to with the scope
channel:moderateHowever the scopes page
https://dev.twitch.tv/docs/authentication/#scopes
is mis leading as it only talks about how the scope works for chat leading to confusion with pubsub operation
"Perform moderation actions in a channel. The user requesting the scope must be a moderator in the channel."
The wording needs to be changed and/or the pubsub topic adjusted to support being able to read moderator events as a moderator
4 votesPubSub was decommissioned on April 14, 2025
-
Don't tell people to auth in a non-standard way Make the docs closer to OAuth specs. The docs say to send parameters to /token (and /revoke) in the query string, but this is non-standard. Twitch supports the parameters in either the query string or request body.
The documentation should prefer the standard approach of sending parameters in the request body.
4 votes -
Webhooks (Un)Subscribe Parameters From: https://github.com/twitchdev/issues/issues/14
Brief description
https://dev.twitch.tv/docs/api/webhooks-reference
the
hub.topicsection is out of date, in the JSON Body ParametersExpected documentation
Just changed it to something like "refer to later in this docs for the available topics"
4 votesWebsub has since been deprecated in favor of EventSub
-
Potential syntax error? Just under the Step 4 header, on line 11 of the code, the html tags open with '<tr><th>' and end with '</td></tr>' and I'm wondering if it's meant to be '</th></tr>' ? if not that's no issue, I'm not the most used to HTML, it just seems odd that it would close with a different tag without an explanation.
3 votesWe're going to rewrite this tutorial at a later time
-
Adjust line number for referenced code I think that the Twitch Extension Helper Library is embedded on line 43 of config.html rather than line 10.
3 votes -
Typo There's a typo in the paragraph that starts:
Follow the Authorization code flow example to get a user access token for the <BOT_USERNAME> Twitch accountYou have
chat%3Aread+chat&3Aeditwhen it should bechat%3Aread+chat%3Aedit3 votes -
Scope missing - channel:send:events Missing documentation for channel:send:events scope.
3 votes
- Don't see your idea?