961 results found
-
Remove jQuery from the GA Example The examples for Google Analytics suggest using jQuery. Which is extra bloat if an extension hasn't use jQuery to start with and can lead to confusion
4 votes -
API to retrieve a users twitch games library The twitch apps games screen is pretty limited. Many have over 100 games on there by now. So I would like to be able to build my own web app and let users log in via twitch and browse their claimed games collection where I can provide filters and search for games using whatever data is available about the games. To do this there must of course be an API where I can retrieve the game list and meta data about them.
4 votes -
Unfollow category/game from API There's currently no way to unfollow a game from the API, in any of the existing APIs (helix, v5, v3). You can follow a game in v5, but not unfollow. Helix has nothing related to games/category. The website itself uses GQL.
4 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
4 votes -
Channel banners made available through the API? Could the channel banners for each user be made available through the API
4 votes -
Hosting API Allow developers to update autohost lists and set the current host via REST-based API.
4 votes -
z-index issue on search Search results are behind images on the main docs page
4 votes -
PubSub Channel Points Data Layout Cleanup Right now, most of the PubSub topics are inconsistent with each other (understandably so). This, however, is focusing on cleaning up some of the ChannelPoints event data that is either unnecessary, redundant, or unclear:
As a note, the information stripped away from the structure is not invalid data, but rather data we likely don't need per message and instead should have a fetch api like manner. One example is the image objects that are likely to never change in the lifetime of a reward. This would save needless encoding as well as any data costs there may be on either…
4 votes -
don't assume gender of viewers in documentation Extensions Manager Overview -> Capabilities -> Request Identity Link
Description refers to viewer as a male ('his'). This is likely to offend some people?
4 votes -
game missing There's no gameid or gamename in the helix get videos endpoint.
Its a bit weird that you get all the information except what's actually being played in the video4 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
}4 votes -
Search is missing from the Embed landing page https://dev.twitch.tv/docs/embed
is missing the docs search function top left/first item in the nav
4 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 endpoints4 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 votes -
include `game_id` in onContext not just the game name game_id would allow an Extension developer to make further API requests for a game with the required ID.
4 votes -
Include the user displayName in extension helper Include the displayName in the javascript helper without asking any special permision or without doing any special function (like using bits).
This value it's only available if the user send bits and the transaction get complete.4 votes -
4 votes
-
Product SKU management in Monetization section of developer platform Currently the management of extension SKU's is only done via the Developer Rig.
Since the rig is an optional, many people are developing / testing without using it & the fact that its a development environment, its a strange place to place/manage production SKU's. These would be better managed from the platform itself under the Monetization tab of each Extension.
4 votes -
Show currently-streaming Authorized Broadcaster information in Channel API It seems that it’s currently impossible to determine who is streaming to a shared channel using the Authorized Broadcaster feature. I tested on my own channels and it appears as if the https://api.twitch.tv/kraken/channels/<mysharedchannel> endpoint does not include any information on the authorized broadcaster streaming to that channel.
Is this something in the works or planned? It would be very helpful for building extensions and bot commands for shared channels.
Note: when adding an email address to the authorized broadcaster list, it does check that the email is associated with a valid Twitch account, so this information should be available…
4 votes -
Add parameter to "Get User Emotes" to return only channel-usable emotes Thanks for the new "Get User Emotes" endpoint.
Here's a bit of an issue with it though. Currently when specifying a channel via "broadcaster_id" it returns the emotes the user can use in all channels and the emotes the user can use only in that channel. That's convenient if I only need to consider a single channel because it's all in a single request.
However if I need to know this information for several channels, I am forced to request the globally usable emotes again for each channel, which can be a lot of requests. As an example I have…
3 votes
- Don't see your idea?