369 results found
-
[Prediction API] A trigger for each or group of predictors I would love to have as an extension of the recently released Prediction API a way to be notified (EventSub or webhook) when someone just spent some channel points in a prediction.
I understand that for big channels a lot of notifications could be sent at the same time, but why not at least merging some notifications in one to bring down a bit this issue?
It could be an array of
predictor objectswith defined max amount of objects per notifications (let's say 100, if 1000 predictors only 10 requests would be sent by the API).The difference with…
2 votes -
Missing information Okay, I got the user access tokens... not how to use it? The page ends without a word...
(like how to get what user is the one who accepted the request).
Also the scope list is not full - Discord use other roles as well, not mentioned in that docs.2 votes -
Add Reason for Bots in Block API The Developer APIs are often used to resolve relationships with sets of accounts used in follow bots through the Block User Endpoint. It would be useful if we could expand the reasons to allow developers to programmatically report bot accounts to help Twitch in removing these accounts. We are all actively building systems to help combat this issue on behalf of Twitch, so let us do our best to help your team.
2 votes -
Implicit Code Flow Samples First of all, thank you for providing developers with valuable tools and apis for twitch. I greatly appreciate the code samples that were provided, however I noticed that there was only a code sample for the authorization code flow. I feel that developers would greatly benefit from examples of how best to work with the implicit code flow. I know this has been an issue for me. For example, if you create an electron application with a modern javascript framework that manages routing, the redirect part of code flow becomes a sticking point. Most of them will use localhost for…
2 votes -
Include eventsub subscriptionevent user message Include subscription message with the subscription event to be consistent with how bits include messages in the event.
2 votes -
Get Active Extension Version info In order to send a chat message via https://dev.twitch.tv/docs/extensions/reference/#send-extension-chat-message you need to know the current active version of your extension. There's no way to retrieve information about your extensions' versions.
There's one way which is kind of roundabout, by first using
/extensions/${CLIENT_ID}/live_activated_channelsto get a list of users, then using/helix/users/extensions/liston one to find the extension again and get its version there.This could be much quicker to find if
live_activated_channelshad aversionfield with the live extension version (it only ever returns a list of channels using the live version).There could also be a
/extensions/${CLIENT_ID}/versionsendpoint…2 votes -
Add the total field to the helix/subscriptions endpoint Just like the /helix/users/follows endpoint, I would like the /helix/subscriptions endpoint to also provide the total results in addition to the next and previous links.
Currently I have to recursively go through all the subscriber pages, 100 par 100, and add up for each one. So I make for my 12,000 subscribers not far from 120 calls which, on the one hand overloads the service and uses part of my call quota, and on the other hand take almost a whole minute to execute.
This is a certain burden for our two sides, as a "total" field would solve all…
2 votes -
Get the latest subscriber The endpoint
/helix/subscriptions?broadcaster_id=USER_IDdoesn't return the data from the most recent to the oldest subscriber.We could maybe use
/helix/subscriptions/events?broadcaster_id=IDbut the data here apparently doesn't last more than 5 days or so. This doesn't work for small streamers who don't have a lot of subscribers coming on a daily basis, for example.Suggestions:
- Create an "order" parameter to the first endpoint, so we could use like
/helix/subscriptions?broadcaster_id=USER_ID&order=desc&limit=1 - Make the second endpoint return the latest "forever".
The first endpoint seems buggy, the data being returned comes in random order and the pagination cursor is always present, even if I clearly…
2 votes - Create an "order" parameter to the first endpoint, so we could use like
-
Channel Points API Suggestions There should be a way to at least enable/disable or pause/unpause rewards that the Client-ID used didn't create. This makes sense since if I'm a moderator I can pause/unpause events that I didn't create for the channel in question. Even if it's a separate endpoint to prevent different bots from "writing over each other" I think this would be the best possible feature to add.
Possible bias: This would make my Channel Points Rewards (Twitch CPR) Game Profile system just that much slicker. ;)
Best part; Could just be a paired-down version of the current "get" function of channel point…
2 votes -
Expose endpoint for total points a user has I would like an option to return the amount a points a current user has.
2 votes -
Allow request clips/videos with broadcaster_id AND game_id Allow to request clips/videos on multiple required query paramters (broadcasterid & gameid).
Exemple: https://api.twitch.tv/helix/clips?broadcaster_id=xxxxxxx&game_id=xxxx
2 votes -
Helix followed channels end-point should show if channel is live Currently requires two un-needed requests https://dev.twitch.tv/docs/api/reference#get-users-follows and https://dev.twitch.tv/docs/api/reference#get-streams
(Instead they could just include a ‘live’ parameter in the first request.2 votes -
Need filter by language in game clips Helix don’t have for game clip by laguage param filter.
Helix api must need it for the other country.
Thank you.
2 votes -
Viewer Data Storage for Extension Overlays/Components/Panels In the context of a Twitch Extension Overlay, the API needs a way to set key value pairs for viewers of a channel not using cookies. Chroma incognito blocks setting local storage and cookies. This would be used to store overlay settings like widget sizes and positions. That way when the page refreshes, the overlay elements would persist their placements. As the great BarryCarylon said "... like Redis for Twitch Extensions".
2 votes -
Clone Custom Reward The ability to specify an existing reward that exists as a basis on creating a new reward would be useful. (This would clone the image/other set parameters as well to the new reward)
Use case:
Channel points to pick a "team" the user would be in.
Today there are three teams, so clone the pre set (disabled) one three times.
Tomorrow there will be four, so clone four times.Image would be the same for all four.
2 votes -
Provide a Helix endpoint to list reward templates created by user, and eventually see the (done, claimed, refunded) I would like to have a way to access a list of CHANNEL REWARDS available for a given channel. Without authentication would be nice, as anyone can see it in the website regardless.
Another additional data provided if the API call is authenticated with the said channel, would be to see the status of the claims (Accepted, pending, refunded) so that the projects based on those can know if it was accepted or if it can be safely removed, in case of a refund.
2 votes -
Inconsistency between Channel Points API and PubSub Redemption Topic When PubSub returns rewards, it references
channel_idwhilst the Beta API Endpoints call itbroadcaster_id.As a Developer, i prefer to be able to parse the same object from different sources in the same way. The discrepancy in naming prevents this / makes it slightly less performant as a distinction needs to be made.
2 votes -
Twitch Connect - app ids shared in api At the moment I have not found any way to get users app id (in my case Riot Account ID) which would allow me to authenticate user using Twitch API and at the same time make sure that user owns this Riot Account. Currently Riot does not support their own way of authentication for third-party developers, therefore Twitch would be great in this case if they shared app ids connected to the Twitch accounts.
2 votes -
Add GET https://api.twitch.tv/extensions/<client ID> as a documented endpoint If you call GET https://api.twitch.tv/extensions/<client ID> you get a JSON back with the information about the extension. This is currently undocumented, but it would be a real useful took for discoverability and management, but being undocumented, it wouldn't be wise to use in a production environment. If this endpoint is planned to be kept, can it be added to the documentation for our use?
2 votes -
fg ghj
1 vote
- Don't see your idea?