162 results found
-
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 -
Documentation is misleading The example and/or documentation of the "Channel Points Event Message" seem to be wrong/misleading, because the example reply does not match the structure of "Message Parameters: All Messages"
3 votes -
Modify Channel Information says "Query parameters" example post says JSON blob https://dev.twitch.tv/docs/api/reference#modify-channel-information
The example calls uses JSON, but the documentation talks about Query String/URL encoded form.
Docs should cover both possibilities and examples should cover both methods
3 votes -
Enabling Drops This guy does not resemble reality. Part 4: Enabling Drops; Click Your Console ( Where is it, I clicked Your Dashboard); Click Drops ( Where is it? How am I suppose to find it?).
Not approvable3 votes -
Update the page This page seems extremely out of date and the example deep links given don't work on tvOS.
2 votes -
Emotes referred to as numbers, where this is no longer true The PRIVMSG Twitch Tags documententation
https://dev.twitch.tv/docs/irc/tags#privmsg-twitch-tags
says
Information to replace text in the message with emote images. This can be empty. Syntax: <emote ID>:<first index>-<last index>,<another first index>-<another last index>/<another emote ID>:<first index>-<last index>... emote ID – The number to use in this URL:Due to channel point modifications, this is no longer true, as emote's are no longer always numbers, they can be xxxx_hf for example
5 votes -
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 -
Embed documentation doesn't mention the SSL requirment https://dev.twitch.tv/docs/embed/ and it's child pages mention the requirements for parent but never SSL
3 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 -
Fix TMI JS example with Promise handling https://dev.twitch.tv/docs/irc#overview
Row:
client.connect();Should be replaced with:
client.connect().catch((err) => {console.log('Connection error!', err)});
or smth like that.Let's show users how to write good code, and show them, that all Promises should be handled. Unhandled promise rejections is bad!
Tmi.js Library also have connect example which contain promise handling
7 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 -
Get Broadcaster Subscriptions Events From: https://github.com/twitchdev/issues/issues/8
Brief description
The subscription events API is documented as a Webhook topic. but not as a API Endpointhttps://dev.twitch.tv/docs/api/webhooks-reference#topic-subscription-events
It used to be in the documentation but is missing
Expected documentation
https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptionsBut for
https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions-events8 votes -
msg-id tags page outdated/incorrect From: https://github.com/twitchdev/issues/issues/68
Docs location: https://dev.twitch.tv/docs/irc/msg-id
bad_ban_global_mod&bad_timeout_global_modare gone for as far as i know (ref: https://blog.twitch.tv/en/2018/12/13/thank-you-global-moderators-4d44cfccf22/)Missing notices for vip events (
vip_success,unvip_success,no_vips,bad_vip_grantee_banned,bad_vip_grantee_already_vip,usage_vip&bad_unvip_grantee_not_vipMight have missed some.First line says "These tags apply to both the" and than only names one thing.
usage_untimeout has "/raid <username>" in the message.
7 votes -
don't assume gender of viewers in documentation Extensions Manager Overview -> Capabilities -> Request Identity Link
Description refers to viewer as a male ('his'). This is likely to offend some people?
4 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 -
The Validate requests endpoint omits the expiry from the example response URL
https://dev.twitch.tv/docs/authentication#validating-requests
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>"
}should be
{
"clientid": "<your client ID>",
"login": "<authorized user login>",
"scopes": [
"<requested scopes>"
],
"userid": "<authorized user ID>",
"expires_in": timeInSeconds
}4 votes -
Fixed position or better visibility for important announcements As per a request from Barry, it would helpful if any flagged messages on a page were fixed or visible when loading a bookmarked section. For example, right now there is an important message on the API reference page about OAuth requirements for Helix, but if someone goes directly to https://dev.twitch.tv/docs/api/reference#get-streams, they will not see this message currently.
3 votes -
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?
2 votes -
Webhooks topic(s) don't note required oAuth From: https://github.com/twitchdev/issues/issues/59
Brief description
Mod Change and Channel ban Change events don't note the required oAuth scope needed for the topic
https://dev.twitch.tv/docs/api/webhooks-reference#topic-moderator-change-events
https://dev.twitch.tv/docs/api/webhooks-reference#topic-channel-ban-change-eventsExpected documentation
Add, (similar to
Topic: User Changed)Authentication User Access Token must have the `moderation:read` for the user in questionAdditional context or questions
5 votes
- Don't see your idea?