130 results found
-
VOD audio track URL
Document URL or port for streaming VOD audio track too!
For context, I'm livestreaming using FFMPEG because OBS is quite heavy if I want to stream in my Chromebook (btw I'm using NixOS instead of ChromeOS)1 vote -
If I need Extensions Onboarding, link to it.
You have error messages that tell me I can't do [insert a variety of things here] until I have completed something like "Extensions Monetization Onboarding." The error message fails heuristics because it doesn't let me fix the problem. It says I need to do something but doesn't give me a link or way to do it. That seems like a huge mistake, but with the forums FULL of people complaining that they can't find it either, I'm wondering if it's a dark pattern and done on purpose.
If there is a workflow that requires me to move through certain steps,…
1 vote -
Documentation is misleading at best
This information is incorrect. The panel and component extensions fail when self hosted with https making it useless to try and test on twitch as it does not function at all. Please update this page or remove it so that people do not attempt to make extensions only to have your code completely ruin the process.
1 vote -
Pubsub Docs: benefit_end_month
This evening I received a resub over pubsub for 3 months in advance. Rather than the documented "multimonthduration" field, that was set to 0 and a new "benefitendmonth" field was returned. This can be used to calculate the number of months, but I can't find any mention of it in the developer docs.
1 vote -
EventSub subscriptions are missing the optional "after" parameter for pagination
There is no explanation on how to use the pagination cursor for EventSub subscription GET requests.
Apparently the cursor can be appended in a request as the "after" parameter, but I feel this should be stated in the optional query parameters, as is the case in the Twitch API reference (e.g. https://dev.twitch.tv/docs/api/reference#get-extension-analytics).1 vote -
Set Up Wording
It would be worth mentioning that in order for developer to see the extension changes, "Live Config Path" has to be filled in with "index.html" as well. Since I was logged in with my streaming account (I assume most of them will be streaming accounts if you are testing on your own profile), I was not able to see the changes.
1 vote -
Game developer playbook clip not playing
On https://dev.twitch.tv/gamedevelopers/development embedded clip is ot configured properly
1 vote -
Publish Official Typescript Typing's for all Data Models
It would be very easy to build and design for if there were official typing for all data endpoints. The data between all the different API's for the same data isn't consistent, and with event sub, since it no longer relies on the underlying Helix endpoint, that data can now be different too. This will also mitigate typos on the docs which causes huge headaches when trying to code for API responses and the data not working, or missing fields. The typing can specify which fields are required and which are optional, so when designing your app, you can easily…
1 vote -
Incomplete/Incomprehensible Step?
why does the documentation not specify how the extension is including the common.js script? How is common.js capable of knowing DOM-elements that are in panel.html?
1 vote -
Examples
Add extra details on examples about how to do request this topic. Your examples wrong or missing.
1 vote -
Please add actual code instead of images in the documentation
Please add actual code instead of images in the documentation. It would be much easier to copy it. Example: https://dev.twitch.tv/docs/tutorials/extension-101-tutorial-series/config-service
1 vote -
email claims missing
Although I set
user:read:emailin the requested scope, neither the ID JWT nor the userinfo contains the email claim. What must we do to make this take effect?1 vote -
Non-Extensions PubSub topics also are supported.
https://dev.twitch.tv/docs/extensions/reference#helper-viewer
states for the "twitch.ext.listen" function/callback
Non-Extensions PubSub topics also are supported.
This is no longer true as every non extension pubsub topic requires an Authentication token, and the listen function doesn't provide a way to specify a token.
Or the documentation is unclear on how/which non extension pubsub topics are supported
1 vote -
cURL examples
The curl examples have done the same thing as the most recent batch of API endpoints that were added to helix and used, long form headers which is inconsistent with the rest of the API documentation
curl --location --request GET 'https://api.twitch.tv/helix/channel_points/custom_rewards?broadcaster_id=274637212&id=92af127c-7326-4483-a52b-b0da0be61c01' \
--header 'client-id: gx2pv4208cff0ig9ou7nk3riccffxt' \
--header 'Authorization: Bearer vjxv3i0l4zxru966wsnwji51tmpkj2'compared to
curl -H 'Client-ID: uo6dggojyb8d6soh92zknwmi5ej1q2' \
-H 'Authorization: Bearer cfabdegwdoklmawdzdo98xt2fo512y' \
-X GET 'https://api.twitch.tv/helix/analytics/extensions?type=overview_v1&extension_id=abcdefgh&started_at=2018-03-01T00:00:00Z&ended_at=2018-05-01T00:00:00Z'A more of a general issue as docs should be consistent with the examples across the board
1 vote -
Missing client_secret failed curl windows/wsl/cmd
This POST request - if attempted with curl in CMD or windows subsystems linux, you need to escape &clientsecret &granttype with preceeding escape\
e.g.
otherwise you WILL get missing client_secret regardless what you try, nothint about the actual curl gives you any hint regarding this.
1 vote -
Authentification desctription isn't descriptive enough
Description in "Getting tokens" isn't very clear and missing a link to "Getting Tokens: OAuth", where it's all explained in detail. That does confuse people
1 vote -
Update the page
This page seems extremely out of date and the example deep links given don't work on tvOS.
1 vote -
Complete Response Codes in Twitch Docs
It would be great if we could have a list of the status codes and their reasons so we can write code to prepare for handling those errors, instead of logging them and dealing with them as they happen - for all endpoints. These exist, for the most part, in a lot of the newer endpoint documentation, but a lot of the older endpoints were rushed in their documentation and we have little information on what responses to expect. Sometimes we get 200s, 202s, 400s, 410s - and having to just "wait" or try to plan for them is a…
1 vote -
Missing docs on OAuth for initial step by step guide
The step by step guide does not reference OAuth tokens yet they are required to do an API request, please update the guide to include info on this.
1 vote -
More information about 'id' uniqueness
More information is required about the uniqueness of id. Is it unique forever (i.e. there will never be two messages with the same id) or is it just guaranteed unique within a timeframe?
1 vote
- Don't see your idea?