164 results found
-
Missing Params in OIDC I think you are missing
force_verify as an optional param on the OIDC authorize, ( its working just not documented)1 vote -
add extensions equivalence in migration page could you add the extensions equivalence?
1 vote -
Fix tmi.js Error when you trying to do !dice
Cannot send anonymous messages.
bot.js:341 vote -
Organize this better, fill in the blanks Who wrote this? The author frequently jumps from point A to point Q.
1 vote -
See scopes Would be nice to see an example with more than one scope. If I separate them with a space, I only gain access to the first one in the list.
1 vote -
PubSub Documentation Formatting In the subscription fields definition, both cumulativemonths and streakmonths are listed as strings when they are very clearly integers.
Further, it would help greatly with readability if the fields were listed in the order they appear in the supplied JSON snippets.
1 vote -
Incorrect documentation for Predictions The Predictions documentation has incorrect information listed for how the Top Predictors are defined. The documentation says the list contains a two-level class called "user" and all properties are below that (EX: "user.id"). However in reality, there is just one class that contains all the information and the "user" part is appended in front of a few relevant properties (EX: "user_id"). Screenshot below for comparision:
1 vote -
docs revision Can you please double check the meaning of the sentences covered in this page (ex: Send the user you want to authenticate to your registered redirect URI. -> you dont't send them to the redirect URI but to the Twitch uri under the cited pharagraph) And the 'token+idtoken' is not equal to 'token%20idtoken' (the 'token id_token' is) the '+' signs encoded to '%2B' which trows an error whereas the ' ' (space) encoded to '%20' which returns the desired result.
1 vote -
make the docs better and more simple to understand for new users. this site is awfull cause the explenation of the api is trash.
1 vote -
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 -
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 -
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 -
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
- Don't see your idea?