154 results found
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
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
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
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
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
Add extra details on examples about how to do request this topic. Your examples wrong or missing.1 vote
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
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 supported1 vote
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'
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 board1 vote
This POST request - if attempted with curl in CMD or windows subsystems linux, you need to escape &clientsecret &granttype with preceeding escape\
otherwise you WILL get missing client_secret regardless what you try, nothint about the actual curl gives you any hint regarding this.1 vote
اريد الدخول بدون تسجيل1 vote
Under the PRIVMSG tags, there are some messages that only have tags and have no other message parts with it (i.e. there is no PRIVMSG, no channel, no message)0 votes
WHERE IS MY OAUTH TOKEN?0 votes
https://dev.twitch.tv/docs/extensions/designing still contains the text annotation "TBD graphic", where there is currently no graphic0 votes
- Don't see your idea?