963 results found
-
Link to docs from developer console Currently, I find the docs hard to get through, although most documentation is there. It would be nice if you can go to the part of the docs that you might need, at the moment you are having a choice. For example when choosing what type of extension you want, that it will have a link to that specific documentation. Let's say you have chosen Panel, you then get a link to a/some of the example repositories for a Panel, the test channel, and a link to the documentation for creating a Panel.
3 votes -
"Recommended channels/streams" API endpoint. Would love an API endpoint for "recommended channels".
6 votes -
10 votes
-
Viewer Only Extensions I was thinking, not all extensions need to be tried to a specific channel experience, and don't always interact with the broadcaster at all. Extensions like the chat translator, or maybe a TTS chat for viewers who can't read well, or visually impared, it would be great to have for users on every channel, not just channels where the broadcaster decides they want to use it. My idea is to have extensions that the view can enable on every channels, and possibly have the panel for viewer extensions be where the chat is, and possibly take up the bottom half…
15 votes -
13 votes
-
Signed Transaction Receipt missing from Bit Transactions API On the new Helix endpoint, https://dev.twitch.tv/docs/api/reference/#get-extension-transactions and therefor https://dev.twitch.tv/docs/api/webhooks-reference/#topic-extension-transaction-created the signed receipt that comes with onTransactionComplete from the JS Helper is missing. In order to audit and avoid man in the middle attacks, a signed JWT that can only be verified with the client secret should be sent on all endpoints sending monetary transaction data.
5 votes -
1 vote
-
Ordering by date of helix endpoints Being able to order some of the Helix endpoints by date would be useful
Follower for example would need in some cases 11k+ calls to the follower endpoint to just get the 100 followers who had followed for the longest time.
This would also be good in the subscription endpoint if cumulative and streak get put into the Helix API
10 votes -
Include username in onAuth callback when a user has granted ID access. Some third-party developers request id access on their Extensions just for the purpose of getting a viewer's username to build a more personalized experience. The only way to do so is by relying on the Helix user endpoint on their EBS. The Helix team already modified any payload that has a user id to also deliver a username and save developers the extra step of using the /users endpoint, so it's natural for Extensions to follow that path.
9 votes -
9 votes
-
Add functionality to query broadcaster id and user id for the Bits transaction API It would be convenient to have the ability to query Bits transactions based on broadcaster id and user id. This is extremely helpful for Extensions with lots of transactions and saves on calls to the API that would be necessary for paginating until the desired transaction is found.
9 votes -
Add subscription status to Viewer's JWT Add subscriptionStatus to extension JWT. Currently subscriptionStatus is in Twitch.ext.viewer. With it in the JWT, it can be verified by an extension backend.
15 votes -
Add the bits:read scope to bits enabled extensions I'm looking to add functionality to an extension where all bits count but bits within the extension have a weighting against those that aren't. I have my own bits transactions through the transactions endpoint but at the moment I have to ask for the scope separately. As my extension is already asking for the
channel:read:subscriptionsI thought it may be a good option to add this as an extra scope to ask for or possibly ask for within the same auth loop as the subscription read7 votes -
Add viewer and channel count in /helix/games/top Add viewer and channel count in /helix/games/top response. This information is currently not available in Helix.
11 votes -
5 votes
-
Streamer whitelist removal after extension is live - [Beta release] Currently, if you launch an extension with a streamer whitelist, there is no way to remove this whitelist once the extension is live.
I would like to suggest being able to remove (And only remove not add) the streamer whitelist once the extension is live. This will enable doing 'beta-releases', which is a very common rollout practice and has a lot of benefits for the developer.
In this way a developer can release an extension to a set group of streamers who want to participate in the beta test.
Once the developer has determined that things look good and it…
6 votes -
Allow filtering the JSON API response For example, the YouTube Data API has the "fields parameter" to accomplish this, an example being: items(userid,username,title)
https://developers.google.com/youtube/v3/getting-started#fields
Thanks!
3 votes -
New Twitch API returning empty results The New Twitch API needs serious attention. I worked considerable with the V3 API and that was rock solid. I'm having a difficult time with the new API. It has a lot of quirks.
My biggest issue now is that certain calls return an empty response with certain parameters.
For example, if I try to filter streams with a gameid and language this will return a result with 0 items sometimes while other times it will return the correct results. The behavior is very inconsistent.
https://api.twitch.tv/helix/streams?gameid=33214&language=enIt works 100% of the time without the language parameter.
https://api.twitch.tv/helix/streams?game_id=33214It…
1 vote -
Pull boxart from Giantbomb Boxart used on a category's Giantbomb page should be automatically set as the boxart on Twitch.
1 vote -
Allow game developers to rename a game Allow game developers to rename a game without going through customer support agents.
Right now I am trying to go through the process of updating the game name, and it has been a **** for 6 months already. Took a month go get the update happen on GiantBomb, waited few months for Twitch to synchronize, which didn't happen, then started writing to support agents.
First reply to my ticket was 2 months after I opened it. Support replied with a canned response about renaming a user...
After reopening the ticket, several weeks later I get the ticket closed again, with…
1 vote
- Don't see your idea?