203 results found
-
Add the IGDB game ID to the Helix Games Endpoint Now that Twitch is utilizing IGDB instead of Giantbomb.
Please add the IGDB Game ID to the Helix Fetch Game endpoint.
https://dev.twitch.tv/docs/api/reference#get-games
https://api-docs.igdb.com/#gameThen we can easily lookup a game on Twitch with the game on IGDB without getting lost in search/selecting the wrong one with a similar name
14 votesIGDB ID is now available in the responses for "Get Games" and "Get Top Games.
-
It is unclear that "Authentication none" means "any token" Some endpoint in the docs say "authentication none" leading to some confusion
https://discuss.dev.twitch.tv/t/getting-top-games-in-python/28256/
6 votes -
Missing info In step2, it says nothing about:
--header 'Authorization: Bearer 2gbdx6oar67tqtcmt49t3wpcgycthx'
It is in a different page, what describe how to get your app id. Should be linked or copy that info to here.1 vote -
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 -
1 vote
This has been clarified in the doc. “Updating to CANCELED will refund the user their points.”
https://dev.twitch.tv/docs/api/reference#update-redemption-status -
Get Custom Rewards doesn't say which Rewards were created by the calling ClientID There should be a field to indicate the owner "clientID" or a "mine: true/false" to represent if the rewards returned by "Get Custom Rewards" belong to the calling clientID or not.
OR
add an optional query string parameter
| name | required | type | description
| -------------------------------------------------------
| mine | no | boolean | if true only return rewards created by this developer/ClientID3 votesonly_manageable_rewards field was added to GET Custom Rewards endpoint. When set to true, only returns custom rewards that the calling client_id can manage. Defaults false.
https://dev.twitch.tv/docs/api/reference#get-custom-reward -
Authorization types and how to get them isn't clear Please pleas please provide a link or something leading to this documentation: https://dev.twitch.tv/docs/authentication/getting-tokens-oauth#oauth-client-credentials-flow
I spent a while trying to figure out how to get a Bearer authorization with no luck, I feel like it should be shown how to do on this page.
1 vote -
Twitch-Notification-Id header documentation The documentation mentions "a unique ID" that is included with each notification, but doesn't mention the header name.
The page should add documentation for the "Twitch-Notification-Id" header.
2 votes -
Extensions package.json HTTPS env variable update In the section for using create-react-app and providing the environment variables for the start script, these docs state using "HTTPS=on". It should be "HTTPS=true" though.
1 vote -
Provide a way for developers to test features which are Affiliate only. Features like Channel Points are restricted for Affiliate accounts only.
The fact that not all developers are streamers themselves too, makes it harder to test features like PubSub on the channelpoints topic. It makes them dependent on other affiliate streamers to test their codebase.
It would be nice if it was possible to have alternative ways to access those. either in a developer sandbox mode for testing, or by a waiver of the regular affiliate requirements for developers.
31 votesTesting Affiliate/Partner events is now possible with the Twitch CLI. See comments for more details.
-
Entitlements Webhook Docs On the Drops 2.0 documentation it states "When a viewer claims a Drop, you can call the Entitlements API to get viewer entitlement data using webhooks. " Yet there are no references to a Webhook Topic for the Get Entitlements endpoint.
Either the Drops 2.0 page is erroneous and there is no webhook, or the Webhook Reference page needs to be updated to include that topic.
1 vote -
Embedded Experiences Requirements - needs spacing on the bullet points The documentation on
https://dev.twitch.tv/docs/embed/
for "Embedded Experiences Requirements" is badly formatted
1 vote -
Add Helix endpoint to get Channel Teams The "GET /kraken/channels/<channel ID>/teams" endpoint is currently missing in the Helix API.
I propose to either
a) add the teams to the "GET /helix/channels" output, or to
b) add new team endpoints to Helix altogether. (Teams need some love!)5 votesEarlier this year, we added Get Channel Teams and Get Teams to Helix.
-
Channel Badges Please provide an official API to get
- Subscriber Badges
- Bits badges
- Other kinds of badges that are channel specific/modifiers there of
For a channel.
8 votesAt the end of May we added Get Channel Chat Badges and Get Global Chat Badges.
-
broadcaster_name not noted in return values of Get Channel info https://dev.twitch.tv/docs/api/reference#get-channel-information
Omits the description of "broadcastername" and as per https://github.com/twitchdev/issues/issues/3 it's the "dISpLaYNaME" of the caster not the username.
So we have to do a second lookup to get the
login
for embed purposes6 votes -
Next Steps Typo There is a typo at the botton of this page
It says @TwitchDevon Twitter instead of @TwitchDev on Twitter :)
1 vote -
Get Subscriptions Endpoint description is ambiguous The Documentation for the Get Broadcaster Subscriptions Endpoint has a description of
Get all of a broadcaster’s subscriptions.
- This is ambiguous and sounds like it returns the Subscriptions to other channels a Broadcaster has whereas it returns the users that subscribed to the broadcaster.I would suggest changing the description to say
Get all of a broadcaster’s subscribers.
instead.2 votes -
Allow a Reward to be created as disabled As a developer, i want to be able to create a reward in the
disabled
state.This is currently not possible upon creation, as the
is_enabled
parameter is ignored. The documentation currently reflects this correctly.Thus, this currently requires the reward to be created and then a
PATCH
request 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
-
Authentication for oAuth is unclear https://dev.twitch.tv/docs/authentication/getting-tokens-oauth
Both Implicit code flow and authorization code flow label the first step as a "HTTP GET" instead of "this is a link that you need to put on a page for the user you wish to authenticate" or "you need to redirect the user to this page"
Too many people are trying to curl/fetch the URL as the docs seem to label it as a HTTP GET request
2 votes -
bug report "Exchanging bits for a product" section has broken markdown link to /extensions/reference/#helper-bits
1 vote
- Don't see your idea?