701 results found
-
11 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 -
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 -
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 -
Extend Clips related API requests - Way to get clips based on more parameters - for example curator_id, vod_id, ejc It is quite hard to find clips using https://www.twitch.tv/manager/clips page to find clips and API does not offer nice solutions to make a 3rd party application to replace it.
Here are some examples of API request parameters and some of their possible uses.curator_id:
- clip creator can find all their own clips
- broadcaster can find and delete all the clips from problematic viewervod_id:
- find clip compilation material for the streamcreated_at:
- find clip compilation material for the date(and range)
- find throwback clips - "last year this time we did this"broadcaster_id:
- in combination…6 votes -
/helix/moderation/enforcements/status - Return error messages instead of generic 500s When user IDs in the provided data payload do not exists, the endpoint returns a 500 error. Ideally this should return a more detailed error code with an error message related to user IDs.
3 votes -
Standardize Transaction Timestamp in Bits Transaction JWT The given JWT representing the transatction receipt contains a time field that is stringified version of the Golang time object. Parsing in this format is significantly harder than a ISO standard format.
5 votes -
Insight into percentage of users that interacted with extension Looking for a metric that helps determine what percentage of viewers tried out the extension. A developer can track the viewer count on their own, but they cannot guarantee that the extension loaded for each user. A metric is desired to calculate that X% of users interacted with the extension, not just a raw value of unique interactions.
2 votes -
Live Activated Channels w/ Extension Webhook There should be a Live Activated Channels with Extensions webhook to get updates once a channel w/ the Extension goes live- similar to the Stream Changed webhook, this would reduce the amount of polling needed.
5 votes -
Drops Sandbox Provide a sandbox to test Drops integrations.
3 votes -
subscriptions revshare model bits revshare is obviously not enough to build a sustainable small/medium business on twitch extensions atm (except 1-2 examples out of hundreds). reasons behind as I see them - extensions are for small streamers mostly. middle/big ones are not that into extensions as a product category. thus even being featured 24/7 doesn't provide enough viewers to actually get $1000-5000 dev payout for most of devs. not to mention retention aspect.
moreover streamers are not that eager for bits. their current meta is to grow subs.
so the idea is to provide devs with ability to work with subscriptions and get…
2 votes -
Add clear all button to Extension whitelists Some developers may need to cycle their Extension's whitelist with a big number of accounts. There's already an option to mass add users to a whitelist. So it's only natural to complement it with a mass delete.
1 vote
- Don't see your idea?