84 results found
-
bug report "Exchanging bits for a product" section has broken markdown link to /extensions/reference/#helper-bits
1 vote -
Typo A token bucketalgorithm
1 voteThis has been fixed.
-
Webhooks limits: ambiguous From: https://github.com/twitchdev/issues/issues/65
Brief description
https://dev.twitch.tv/docs/api/webhooks-guide
Limits: By default, each client ID can have at most 10,000 subscriptions. Also, you can subscribe to the same topic at most 3 times.
Seems to be ambiguous to a lot of developers, they seem to think the that "3 times" means they can renew it 3 times then they are SOOL
Expected documentation
Limits: Each client ID can have at most 10,000 subscriptions. Where you can have 3 active subscriptions to a topic at the same time. Where an active subscription is defined as a topic/callback pair.
4 votes -
Locales/language valid options From: https://github.com/twitchdev/issues/issues/31
Brief description
The documentation doesn't advise anything regarding what languages/localses exist/are valid to be called.
For example
https://dev.twitch.tv/docs/api/reference#get-streams
has a
language
query string argument, but doesn't advise what is valid for a langauge.Expected documentation
Document the list of locales of if it matches a ISO, update documentation on endpoints using language/locale with a note about what is valid
Additional context or questions
Raised/queried on discord
https://discordapp.com/channels/504015559252377601/523675960797691915/664243349309620225
3 votes -
1 vote
-
Docs don't mention Token Type Similar to
All documentation should be revised to describe which kind of token and depending on token type what scopes are needed to call each endpoint.
The documentation for the most part only mentions a scope and doesn't describe what kind of token to use
2 votes -
Words missing in docs Missing word(s) in this sentence:
"if the parameters supplied are you receive an immediate 202 Accepted response"
between the "are" and the "you" there's words missing.
1 vote -
formatting broken for example response Formatting broken for example response at https://dev.twitch.tv/docs/api/reference#get-hype-train-events
1 vote -
Chat embed ID parameter example/description Should the ID parameter now be "chat_embed" or the channel name? Parameter description and example code don't match or I don't understand it.
1 vote -
Documentation for 'Get Users Follows' is out of date The documentation for Get Users Follows says: “Authentication: None”, but you get “OAuth token is missing” response when not using an app or user access token.
1 vote -
Missing Client-ID in examples The recent new end points caused the existing documentation to lose the Client-ID from all other examples as is required by the changes to helix.
For Example:
https://dev.twitch.tv/docs/api/reference#get-extension-analytics
curl -H 'Authorization: Bearer cfabdegwdoklmawdzdo98xt2fo512y' \ -X GET 'https://api.twitch.tv/helix/analytics/extensions?first=5'
Getting Started also needs to be updated as it doesn't reference authorization required at all
https://dev.twitch.tv/docs/api, and doesn't cover how to get authorization
1 vote -
Get Channel includes references to information not in the response https://dev.twitch.tv/docs/api/reference#get-channel-information
Refers to
status
anddescription
which are not in the responseAlso mentioned in
https://dev.twitch.tv/docs/api/reference#modify-channel-information
1 vote -
The new documentation uses a different format to the cURL examples curl --location --request PATCH 'https://api.twitch.tv/helix/channels?broadcaster_id=41245072' \ --header 'client-id: wbmytr93xzw8zbg0p1izqyzzc5mbiz' \ --header 'Authorization: Bearer 2gbdx6oar67tqtcmt49t3wpcgycthx' \ --header 'Content-Type: application/json' \ --data-raw '{"game_id":"33214", "title":"there are helicopters in the game? REASON TO PLAY FORTNITE found", "broadcaster_language":"en"}'
compared to
curl -H 'Authorization: Bearer cfabdegwdoklmawdzdo98xt2fo512y' \ -X GET 'https://api.twitch.tv/helix/streams/markers?user_id=123&first=5'
Examples should be consistent
1 vote -
Modify channel: oAuth confusing https://dev.twitch.tv/docs/api/reference#modify-channel-information
Says
Parameter Type Description broadcaster_id string ID of the channel to be updated
When it should say
User ID of the broadcaster. Must match the User ID in the Bearer token.
as per
https://discuss.dev.twitch.tv/t/announcing-the-latest-helix-endpoints-and-hype-train-api/26530/12
1 vote -
IRC NAMES command only ever returns self The IRC documentation states
List current chatters in a channel. If there are more than 1000 chatters in a room, NAMES return only the list of operator privileges currently in the room.
In my testing, I have only ever gotten Twitch to return my own username, even (only) in small (under 1K) rooms.
[@] :eggdroptest.tmi.twitch.tv 353 eggdroptest = #superscientistjhrek :eggdroptest
For example, that room usually has 15-30 chatters (in this case, there were 23 people in it), and several mods, but no names other than my own were returned as part of the 353 message.My suspicion is that perhaps…
1 vote -
Extension viewer Session Token From: https://github.com/twitchdev/issues/issues/51
Brief description
https://dev.twitch.tv/docs/extensions/reference#helper-viewer
documentation wrong:
sessionToken Twitch.ext.viewer.isLinked: string The encoded JWT. This is the same as the token property of the authData parameter that currently gets passed to the onAuthorized callback.
Expected documentation
sessionToken Twitch.ext.viewer.sessionToken: string The encoded JWT. This is the same as the token property of the authData parameter that currently gets passed to the onAuthorized callback.
3 votesCorrected for today’s deployment
-
Get Broadcaster Subscriptions with an App Access Token From: https://github.com/twitchdev/issues/issues/45
Brief description
Get Broadcaster Subscriptions doesn't describe how you can use an "App Access Token" for an extension that has sub status enabled, to use the end point
Expected documentation
Describe that an "Extension App Access token" can be used when a broadcaster has granted the "channel:read:subscriptions" scope via the Twitch Extension Manager
3 votesAdded to today’s documentation deployment
-
Config Service links to wrong reference From: https://github.com/twitchdev/issues/issues/40
Brief description
https://dev.twitch.tv/docs/extensions/building/#using-the-configuration-service
Mentions "twitch api reference" but the config service endpoints are on in the Extension Reference
For extension examples that leverage the configuration service see the new Twitch API Reference. Also, see these repositories:
Expected documentation
Links to
https://dev.twitch.tv/docs/api/reference
but the configuration API is documentedhttps://dev.twitch.tv/docs/extensions/reference#set-extension-required-configuration
3 votes -
Documentation Scopes Page missing moderation:read The scopes page on Authentication(https://dev.twitch.tv/docs/authentication/#scopes)
is missing the documented scope from the Helix Get Moderators
Returns all moderators in a channel.
Authorization
Requires OAuth Scope: moderation:read2 votes -
Typo in docs On page:
https://dev.twitch.tv/docs/extensions/reference#helper-bitsThe 'onTransactionComplete' fields list 'transactionID' (capital D), but you get "undefined" when accessing with capital D. Actual field is 'transactionId'.
A small change, but tripped me up a bit during implementation.
Thanks!
1 vote
- Don't see your idea?