203 results found
-
Get users doesn't mention that an App Access Token works https://dev.twitch.tv/docs/api/reference#get-users
Mentions User OAuth and the optional scope, but doesn't mention that you can use an app access token for this endpoint to get "public" data.
Authentication User OAuth Token Optional scope: user:read:email If this scope is provided, the response includes the user’s email address.Should probably read
Authentication - App Access Token - User OAuth Token any/no scopes - User OAuth Token with scope: user:read:email response includes the user’s email address.7 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 -
Typo in docs On page:
https://dev.twitch.tv/docs/extensions/reference#helper-bitsThe 'onTransactionComplete' fields list 'transactionID' (capital D), but you get "undefined" when accessing with capital D. Actual field is 'transactionId'.
A small change, but tripped me up a bit during implementation.
Thanks!
1 vote -
links no-longer clickable The procedures are no longer clickable at https://dev.twitch.tv/docs/authentication#getting-tokens.
(for a clickable reference see https://web.archive.org/web/20191220122144/https://dev.twitch.tv/docs/authentication)
5 votes -
Missing/incorrect description scopes for GET Helix/Users https://dev.twitch.tv/docs/api/reference#get-users
user:read:email disappeared and user:edit:broadcast now has the email scope's description.
2 votesThis error has been corrected, thanks.
-
Docs don't mention Token Type Similar to
All documentation should be revised to describe which kind of token and depending on token type what scopes are needed to call each endpoint.
The documentation for the most part only mentions a scope and doesn't describe what kind of token to use
2 votes -
Document correction for helix moderators endpoint https://dev.twitch.tv/docs/api/reference#get-moderators Under optional parameter for user_id the description says for users who are banned in this channel for the moderators endpoint.
6 votes -
API to CRUD the new/upcoming schedule Please provide an API for the new upcoming Twitch features (preferrably day 1 would be nice)
Today, I'm here again to ask for an API.
Today for the new/upcoming schedule feature I've heard about
152 votesThank you for the feature request. The Twitch API now includes Schedule APIs! https://discuss.dev.twitch.tv/t/announcing-api-endpoints-for-twitch-channel-stream-schedules/32137/
-
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
-
IRC NAMES command only ever returns self The IRC documentation states
List current chatters in a channel. If there are more than 1000 chatters in a room, NAMES return only the list of operator privileges currently in the room.
In my testing, I have only ever gotten Twitch to return my own username, even (only) in small (under 1K) rooms.
[@] :eggdroptest.tmi.twitch.tv 353 eggdroptest = #superscientistjhrek :eggdroptest
For example, that room usually has 15-30 chatters (in this case, there were 23 people in it), and several mods, but no names other than my own were returned as part of the 353 message.My suspicion is that perhaps…
1 vote -
Doc site not usable on mobile Your entire dev site has no sidebar on mobile so you can’t get to most subpages without digging. Can these be added to a hamburger menu at small resolutions please?
1 voteRotating dropdown arrow has been added to the “contents” button to show the sidebar on mobile.
-
4 votes
-
Thanks This is really very cool. Thank you for taking the time to create such awesome documentation. I am a front end dev for a well know travel website and I appreciate the effort that goes into making this.
1 voteThank you very much!
-
Neither the issues repo or the Dev Uservoice are linked on the Support page https://dev.twitch.tv/support has no links to the dev Issues repository for bugs, or the uservoice for Feature Requests
1 voteUserVoice and GitHub Issues has been added. Thumbnail for docs also updated.
-
fix misleading descriptions This documentation isn't clear enough, it implies that the ID attribute should be set to the channel name, but for whatever reason it has to be set to 'chat_embed' and then the channel name goes in the SRC URL, replacing the 'hebo' text. There's no description of how the 'src' attribute should be presented so this isn't immediately clear.
1 vote -
My "documention idea" is that the documentation has a text formatting bug https://i.gyazo.com/76d10ed7c987ed262276501e25231ac6.png
"
WWW-Authenticate header" vs "WWW-Authenticateheader"EDIT: Another bug here https://dev.twitch.tv/docs/api/webhooks-reference#subscribe-tounsubscribe-from-events
"...if the parameters supplied are you receive an immediate..."
Reads like there should be something after "are".
1 vote -
Documentation Scopes Page missing moderation:read The scopes page on Authentication(https://dev.twitch.tv/docs/authentication/#scopes)
is missing the documented scope from the Helix Get Moderators
Returns all moderators in a channel.
Authorization
Requires OAuth Scope: moderation:read2 votes -
Example/URL is incomplete https://dev.twitch.tv/docs/api/reference/#get-extension-transactions
Unlike other documentation, https://api.twitch.tv/ is omitted from the URL and the example call
2 votes -
Fulfill or Reject Channel Points Redemptions Programmatically Channel points have the ability to reward loyal viewers with real-time influence on the stream. Sometimes such requests may be filtered, which should trigger a rejection (therefore refund).
Right now the only way to do this programmatically would be to use unsupported GQL APIs and risk the wrath of Twitch, or wrap the rewards queue in some way. This is the only blocker (technically speaking) for the workflow, as PubSub does expose enough information to respond to the redemptions automatically.
I've had a proof of concept on my stream which gets redemptions via PubSub, filters the submission for offensive content…
24 votes
- Don't see your idea?