37 results found
-
678 votes
As mentioned earlier today on the TwitchDev Standard Output broadcast, we are moving this suggestion to "planned." We appreciate everyone's patience with this one. Although it sounds simple and we see the value, there were a number of underlying complexities to consider before we had confidence in a path forward and providing a response. We will provide another update when the endpoint is available for testing.
-
Pinned messages API Please provide an API to
- pin existing message
- pin a new message
- unpin a message
Which should work using a moderators token in line with the announced new feature
68 votesWe're planning to add support for pinned messages in the API and EventSub.
-
channel subscriptions to include who gave the gift if it's a gift Extend EventSub subscriptions topic to include information about who gave the gift if it was a gift subscription.
36 votesWe are planning a few updates to subscription payloads, including this item.
-
Please provide an eventsub for pinned messages add/removal Provide a topic for when the pinned message changes/added/removed from a channel
23 votesWe plan to support pinned messages in the Twitch API and EventSub.
-
Swagger / JSON Schema Would be helpful to provide a openapi/swagger document or json schema for the objects here
9 votes -
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 the8 votes -
Add a topic for Roomstate changes including whom triggered it Chat has a number of states, slow mode/follower only mode.
Some moderationg applications involved monitoring for these states and responding as needed, and these applications will currently use PubSub but only in a logging capacity so alternatively connecting to chat for this data is perhaps overkill.
Please provide an eventsub topic that relays
- when/what Roomstate changes (slow on/slow off sub on sub off emote only)
- which moderator/user triggered the change.6 votesWe plan to offer this in EventSub.
-
PubSub Topics: no moderator topic examples/documentation https://dev.twitch.tv/docs/pubsub
Has no examples or documentation for payloads for chatmoderatoractions
6 votes -
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
6 votes -
More detail on obtaining OAuth and OIDC tokens You provide information on how to remove a token, how to refresh a token, and how to define scopes for tokens, but you don't actually have any information on how to request a token, nor any sample code on that or applying token scopes. Given that this step is fundamental to any interaction with the Twitch API, this seems like a fairly major omission.
5 votes -
User banned extensions unload So it seems that when a user is banned or timed out, extensions unload/are unavailable to those users.
This is not documented.
It should be documented somewhere
4 votes -
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
4 votes -
graph syntax not built on deploy The graphs on this page don't look right. The graph syntax is displaying, not the graph itself.
%% Extensions Overview Diagram graph LR Twitch --> | - postMessage - | Extension Extension --> | - postMessage - | Twitch Extension --> | - HTTP - | APIs Extension --> | - HTTP - | EBS[Extension Backend] Identity --> Twitch Chat --> Twitch Memes --> Twitch3 votes -
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
3 votes -
The Validate requests endpoint omits the expiry from the example response URL
https://dev.twitch.tv/docs/authentication#validating-requests
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>"
}should be
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>",
"expires_in": timeInSeconds
}3 votes -
HTTP Response codes unclear From: https://github.com/twitchdev/issues/issues/69
Brief descriptionSome endpoints return a 204 code no content.
But this is only highlighted in the example responses and not in the "main documentation"For example
https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-message
https://dev.twitch.tv/docs/extensions/reference#send-extension-chat-messageEach endpoint documented could be extended to include usual HTTP response codes.
Expected documentation
The expected response code for success when theres no body response
Common non 2xx codes for the endpoints3 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"
3 votes -
Please add window.Twitch.ext.viewer.helixToken Please add a JS Helper function
Which is the equivalent of
window.Twitch.ext.viewer.sessionTokenbut for the helixToken ofwindow.Twitch.ext.viewer.helixToken.2 votes -
Split the Helix API reference into sub-categories As the Helix API reference page (https://dev.twitch.tv/docs/api/reference) is continuing to grow it it is starting to become unwieldly with the number of entries.
It would be beneficial to the docs to create sections for different areas of the API. Appropriate names for the sections are already listed in the API, as at the top of the reference page is a table that has a 'Resource' column which would be perfect for this usage, and that table can remain at the root reference page so that devs can see at a glance what endpoints are in what section, then…
2 votesThis has been on the roadmap, and is planned for early 2021.
-
Modify Channel Information says "Query parameters" example post says JSON blob 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
2 votes
- Don't see your idea?