163 results found
-
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
2 votes -
IRC Landing page/guide -> twitchapps.com https://dev.twitch.tv/docs/irc
As a getting started/IRC docs landing page is confusing new developers
As it references
The token to authenticate your chatbot with Twitch's servers. Generate this with https://twitchapps.com/tmi/ (a Twitch community-driven wrapper around the Twitch API), while logged in to your chatbot account. The token will be an alphanumeric string.
And doesn't reference anything about the "right way" to auth/scopes needed
Until the end of the guide.
Authentication using not a third party site should be more prevalent in the guide.
3 votes -
VIP scope mistake? Hey, it says "/vip /unvip" is under "channel:moderate" scope, wouldn't that be moderator status? because I'm sure moderators can't grant/remove VIP status to a user. Or am I wrong?
2 votes -
email claims missing Although I set
user:read:email
in 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 -
"Registering your App" an Extension is also an App https://dev.twitch.tv/docs/authentication
Says
Authentication involves: Registering your app to obtain a client ID and client secret. Getting a token. This includes specifying scopes, the permissions your app requires. Sending the token in your API request, to authenticate API requests.
But doesn't mention that an Extension is also an Application
This docs fix would be needed on other pages where "registering an app" is mentioned
2 votes -
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 -
Document exact what triggers `viewer.onChanged` https://dev.twitch.tv/docs/extensions/reference#helper-viewer
SNIPPET STARTS
onChanged
Twitch.ext.viewer.onChanged: void function(callback: Function())This function binds a callback will be invoked when the viewer’s status changes (e.g. if a viewer subscribes and changes their subscription status).
SNIPPET ENDS
Cannot tell if broken or only triggers on subscription status change.
IE is it supposed to trigger on
role
changes? If so it's bugged, if not the documentation needs to document what does cause onChanged to be called2 votes -
Capabilities sub pages no clear capability needed It should be more obvious that
Twitch IRC: Commands
needs the commands capability,Twitch IRC: Tags
needs the tags capability, Membership page needs the membership capability.IE:
Literally add a paragraph at the top to the effect of
The Twitch IRC responses outlined on this page requires the connection to have requested the $whatever capability as outlined on the https://dev.twitch.tv/docs/irc/guide#twitch-irc-capabilities Capabilities section of the guide.
4 votes -
Add documentation about how the Chat Filters feature is implemented. Could you please add documentation about how the chat filters feature in web chat is implemented? Other chat client could really benefit from filtering those messages or highlighting them for moderators as suspicious behavior.
To pin point the exact feature I provided screenshots from the official web browser chat:
- in action: https://i.imgur.com/CfzMx0z.png
- and the associated settings: https://i.imgur.com/8dYADBk.png10 votes -
Get Custom Reward Redemptions "missing redemption status" Declares that only broadcasterid and rewardid are required.
A call to
results in
{
"error": "Bad Request",
"status": 400,
"message": "missing redemption status"
}The documentation lists status as not required
3 votes -
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 -
Custom Rewards limit? Pagination Support
None.
There is a limit of only 50 Custom Rewards on a channel at a time.It's unclear if that means 50 active rewards or 50 total rewards. It should be more plain text/clear.
The help article
https://help.twitch.tv/s/article/making-the-most-of-channel-points?language=en_US
doesn't mentioned this limit either.
2 votes -
Document API and IRC tags for replies Web chat users got access to the new "replies" feature, where you can mark your message to be a reply of another message.
My suggestion is to add official documentation on how third parties can use this feature (for sending messages and for parsing received messages to be a reply)
7 votes -
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 -
Userstate in IRC is out of date in docs This is out of date. Update it please.
2 votes -
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
2 votes -
Update the page This page seems extremely out of date and the example deep links given don't work on tvOS.
2 votes -
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…
2 votes -
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.
2 votes
- Don't see your idea?