203 results found
-
Add mod/unmod events and adding/removing editors Mostly for broadcaster tools which have some kind of permission system that allows mods (and now editors) specific access to features. This would remove the need for checking if the user is still a mod/editor.
4 votes -
Error in "Refreshing access tokens" section The actual docs states that "When you make a request with expired or incorrect authorization credentials, the API returns a WWW-Authenticate header (with an invalid_token error) and a 401 Unauthorized status", but the WWW-Authenticate header is not present in the response.
Moreover the example shows a kraken endpoint.
4 votes -
Ability to increase subscriptions limits We run a Discord bot on ~9M Discord servers. It announces streams in Discord servers.
We are subscribed to 1M+ twitch channels using webhooks and managed to get there by taking advantage of the rate-limit bump form you guys provided back then. But it seems like you guys stopped doing that.
Since we hit the limit of subs, we had to change the way we do it and loop over live streams using the API - which is suboptimal since we miss some streams and the announcements are delayed.4 votesWe recently updated our subscription limit logic in EventSub so that limits scale as your application grows. See https://dev.twitch.tv/docs/eventsub#subscription-limits for more information.
-
Correct typing errors in the "Scopes" At https://dev.twitch.tv/docs/authentication#scopes
- "channel:manage:brodcast" is misspelled (should be "channel:manage:broadcast")
- "channel:manage:extension" is misspelled (should be "channel:manage:extensions")As metioned in other posts "channel:read:redemptions" is still missing there.
4 votes -
Allow a Reward to be created as disabled As a developer, i want to be able to create a reward in the
disabledstate.This is currently not possible upon creation, as the
is_enabledparameter is ignored. The documentation currently reflects this correctly.Thus, this currently requires the reward to be created and then a
PATCHrequest to be made right afterwards, updating the just-created reward.Allowing this would, for example, allow "secret" rewards to be created before being "released to the public" or allowing the Broadcaster to utilize the dashboard management page to choose between a set of pre-created rewards.
4 votesThe “Create Custom Reward” endpoint now allows setting the “is_enabled” field. https://dev.twitch.tv/docs/api/reference#create-custom-rewards
-
4 votes
EventSub is our Webhooks solution. We will remove the legacy Webhooks section of the docs when our Legacy Webhooks product is shut down later this year.
-
New IRC tag "msg-params-gift-months" in docs is actually "msg-param-gift-months" The recent announcement "Updates to PubSub Messages and IRC for Multi-Month Subscription Gifting" (https://discuss.dev.twitch.tv/t/updates-to-pubsub-messages-and-irc-for-multi-month-subscription-gifting/26873) and IRC Tags docs (https://dev.twitch.tv/docs/irc/tags#usernotice-twitch-tags) lists the new "msg-params-gift-months" tag, but like all other so far it's actually singular "param" not "params" ("msg-param-gift-months") in reality.
4 votes -
Helix Users docs showing optional scope as required The Helix Users endpoint docs state the "user:read:email" scope as required, although it is an optional scope if you also need the users email returned.
4 votes -
Extension uninstall too prominent On the extensions/manager dashboard page
The options on the "Activated" extensions bottom right is configure and uninstall
Streamers are more likely to uninstall than deactivate as the trashcan/uninstall is too prominent compared to deactivate from slot, for if a streamer wants to deactivate instead.
The uninstall dialog doesn't mention deactivate either, "you are about to uninstall are you sure you don't want to deactivate instead"?
4 votes -
Documentation not updated for oAuth changes on Helix As per
https://discuss.dev.twitch.tv/t/requiring-oauth-for-helix-twitch-api-endpoints/23916
None of the documentation is updated to reflect this change.
Yes it's not required yet. But it's good practice for new developers to be using the new oAuth procedure now
4 votes -
Bring "Get Followed Streams" endpoint to Helix With the actual Helix API, there are two ways to retrieve the authenticated user's followed streams:
First, get user follows (https://dev.twitch.tv/docs/api/reference#get-users-follows) and then get all active streams details, by specifying each user_id individually. If the user is following 300 users, this would require at least 6 requests (eventually one more to get the autenticated user's id). This method is quite inefficient compared to the v5 endpoint.
The second way is to use the "Stream Changed" webhook (https://dev.twitch.tv/docs/api/webhooks-reference#topic-stream-changed). Again, I should first retrieve all user follows (3 requests for 300 follows), and then subscribe to 300 webhooks…
4 votesDocumentation can be found here: https://dev.twitch.tv/docs/api/reference/#get-followed-streams
-
4 votes
-
Webhooks limits: ambiguous From: https://github.com/twitchdev/issues/issues/65
Brief description
https://dev.twitch.tv/docs/api/webhooks-guide
Limits: By default, each client ID can have at most 10,000 subscriptions. Also, you can subscribe to the same topic at most 3 times.
Seems to be ambiguous to a lot of developers, they seem to think the that "3 times" means they can renew it 3 times then they are SOOL
Expected documentation
Limits: Each client ID can have at most 10,000 subscriptions. Where you can have 3 active subscriptions to a topic at the same time. Where an active subscription is defined as a topic/callback pair.
4 votes -
Get All Chat Emoticons From: https://github.com/twitchdev/issues/issues/10
Brief description
Docs state the "images" is an array
{
"links": {
"self": "http://api.twitch.tv/kraken/chat/emoticons"
},
"emoticons": [
{
"id": 115390,
"regex": "TwitchLit",
"images": [
{
"width": 28,
"height": 28,
"url": "https://static-cdn.jtvnw.net/jtvuserpictures/emoticon-115390-src-b577ded8522fc1a1-28x28.png",
"emoticonset": 19151
}
]
},
{
"id": 80393,
"regex": "Kappa",
"images": [
{
"width": 28,
"height": 28,
"url": "https://static-cdn.jtvnw.net/jtv_user_pictures/emoticon-80393-src-cf7c8d03a4c5cb75-28x28.png",
"emoticon_set": 15940
}
]
}
]
}Expected documentation
…{ "_links": { "self": "http://api.twitch.tv/kraken/chat/emoticons" }, "emoticons": [ { "id": 115390, "regex": "TwitchLit", "images": { "width": 28, "height": 28, "url": "https://static-cdn.jtvnw.net/jtv_user_pictures/emoticon-115390-src-b577ded8522fc1a1-28x28.png", "emoticon_set": 19151 } }, { "id": 80393, "regex": "Kappa",4 votes -
Missing User's subscriptions functionality for the subscriptions endpoint On helix we can only get people that are subscribed to a broadcaster, we can't get the broadcasters a user is subscribed to.
So basically we've got V5 channels/<channel ID>/subscriptions.
We are missing V5 <user ID>/subscriptions/<channel ID>.4 votesSome of the requested functionality is available with the Check User Subscription API.
-
Extend get clips endpoint with featured flag May we get an extension for the "Get Clips" endpoint so we can see in the response which clip had been featured?
Also an optional filter for request query that returns all, non-featured or featured clips depending on the passed parameter. By default it would return all clips.3 votesis_featured has been added to the return payload as well as an optional query parameter to get all featured or all non-featured Clips.
-
User ban timestamp A user's banned timestamp when fetching this route https://dev.twitch.tv/docs/api/reference#get-banned-users (When did the user got banned precisely).
3 votes -
Bans/Banned events who did it Similar to https://twitch.uservoice.com/forums/310213-developers/suggestions/42562003-bans-who-did-the-action
But extended to the Helix API.
It would be useful to add who did a given "Ban Event" to the Get Banned Events for "service restart catchup" when using eventsub.
And useful to add it to the main "get banned users" for determining as a moderator using a tool the history or a user and to check with that moderator why that user was banned, but can't since the API doesnt' report who did it.
3 votes -
Allow access to the "Get Channel Chat Badges" endpoint using an App Access Token All of the new emote and badge endpoints can be accessed using an App Access Token except for /chat/badges which needs a User OAuth Token.
I don't see why this endpoint needs a user token since the badges can be viewed publicly on the subs page and It doesn't reveal any private info about a user.3 votesThank you for reporting this issue. This endpoint now supports access with an App Access Token.
-
Game Title for GET helix/search/channels endpoint The "GET helix/search/channels" endpoint only gives the game_id and not the game title, this would mean extra API calls that could be avoided if you included the game name in the response.
3 votesThank you for this request! We added the game_name field recently.
- Don't see your idea?