963 results found
-
/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 -
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 -
Product SKU management in Monetization section of developer platform Currently the management of extension SKU's is only done via the Developer Rig.
Since the rig is an optional, many people are developing / testing without using it & the fact that its a development environment, its a strange place to place/manage production SKU's. These would be better managed from the platform itself under the Monetization tab of each Extension.
4 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 -
Issue with v5/bits/extensions/is-eligible/ API There are two scenarios when using this API which return a 500 from the server, but which should return either a 401 or 400 and a meaningful error code to help point out the issue:
If you have set your productSKU's to 'live', but you're testing in 'Hosted testing', you receive this error. A response telling you that you cannot test SKUs in live mode when in hosted testing would be great.
If your extension is live and you are trying to use bits on a channel which doesnt support it, you will receive a 500 from the server. I…
3 votes -
Allow Developers to Rollback to Approved Extension Versions Allowing developers to roll back a released version to another (approved) version would allow developers to quickly address breaking issues without going through a review process.
87 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 -
13 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 -
Allow Upload of Category Banners in Developer Site Game developers can currently upload only the boxart, but to upload the banner they have to reach out to Twitch to update. It would be nice to have this moved into the site to make it easier to manage.
1 vote -
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…5 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 -
Verified Developer Badge Partners get a verified badge, it would be nice for published developers to get a badge too, maybe after a certain usage requirement of their extension, like how partners have to hit certain limits to become partner, maybe enough usages or page views of the extension will get a dev a badge.
222 votes -
Subs Tenure in Helix We would like subs tenure in Helix in order to use this for merch extensions providing tenure-based merch options.
141 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 -
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 -
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 -
Include follow count in /helix/users Add follow count to /helix/users endpoint. This data is accessible via /helix/users/follows, but would require an additional call.
149 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
- Don't see your idea?