160 results found
-
Some Typos on "The New API" Documentation Hello,
Searching in the documentation of the new API I have found these four small errors. They are not at all severe, but they should be remedied in order to facilitate the use of the API.
- https://dev.twitch.tv/docs/api/reference#get-extension-transactions => Link bad rendered in Markdown
- https://dev.twitch.tv/docs/api/reference#get-bits-leaderboard => typo on OAuth Token, missing O
- https://dev.twitch.tv/docs/api/reference#redeem-code => method missing
- https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions => Scope in wrong format (not labeled)
2 votes -
error in documetation msgid:"usageuntimeout" states:'Usage: “/raid <username>” - Removes a timeout on a user.' and not /untimeout
2 votes -
Link to locustfile for load testing extensions not working The formatting of the link to the locustfile in https://dev.twitch.tv/docs/extensions/load-testing-extensions#run-your-locust-test is not working because there are code tags in front of and after:
2 votes -
Missing/incorrect description scopes for GET Helix/Users https://dev.twitch.tv/docs/api/reference#get-users
user:read:email disappeared and user:edit:broadcast now has the email scope's description.
2 votesThis error has been corrected, thanks.
-
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 -
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 -
Example/URL is incomplete https://dev.twitch.tv/docs/api/reference/#get-extension-transactions
Unlike other documentation, https://api.twitch.tv/ is omitted from the URL and the example call
2 votes -
Linked statuspage does not exist The linked status page does not exist and redirects to: https://www.atlassian.com/software/statuspage
1 vote -
broken link on video broadcast docs link that should show more info about broadcasting technical aspects, https://stream.twitch.tv/ leads nowhere
1 vote -
Twitch Extention Document server.py can not be executed because it is written in Python 2x. Also, changing "start": "HTTPS=true PORT=8080 react-scripts start," causes an error. Wouldn't it be better to modify it to write in .env.
1 voteUpdated snippet to Python 3
-
****** docs Poorly written docs. Nowhere is mentioned when you would use "Client credentials flow", which EXACT situations. Waste of time.
1 voteDocumentation states: "The client credentials grant flow is meant only for server-to-server API requests that use an app access token."
-
Ошибка в команде yarn create react-app example-extension
there is a mistake. Command have to beyarn create-react-app example-extension
1 vote -
Typo There's a typo on the "Running the bot" section of this page: https://dev.twitch.tv/docs/irc/get-started
The last word of the "The bot is running locally..."
It's supposed to be dice, i guess.
I don't want to roll the die lmao1 voteThis page has since been removed
-
Scope delimiter needs to be explicit ':' instead of code &scope=chat%3Aread+chat&3Aedit is not correct. It needs to be: &scope=chat:read+chat:edit
1 vote -
Rate limits with different status between channels This is related to the "Rate limits" section :
What if a bot joins 2 channels, but only has mod status in 1 of them ?
Will the messages limit be 20 for both channels ?
Or will it be 20 for the channel where the bot doesn't have mod status and 100 for the channel where the bot has mod status ?
1 voteThe Rate Limits page was updated with this information and more in 2024:
https://dev.twitch.tv/docs/chat/#rate-limits
-
API Reference Typo Under the Return Values of the Get Predictions Request of the Twitch API Reference, the description of the return value 'outcome.users' has a typo. It should read 'Number of unique users that chose the outcome.' However it says 'Number of unique uesrs that chose the outcome.'
1 vote -
Typo Typo on second bullet point of Specify Configuration Settings: access has one too many 's'
1 vote -
Please add more examples for Ratelimit headers Please provide one example for the Ratelimit headers. Tried a couple of hours without success. Thanks.
1 vote -
Create EventSub Subscription Wrong Response Code On the documentation for creating an eventsub subscription the page claims a success response should have a status code of 201, but the actual status code returned on success is 202.
Either the documentation should be changed to refled the API, or the API changed to reflect the documentation.
1 vote -
Disambiguate the "Legacy" API in documentation This page should mention that "v5" and the "kraken" api refer to the same thing. Me and my friends always used "Kraken" to refer to this api, it's in the endpoint its self.
I'm sure we are not alone in this, please mention that v5 IS the Kraken endpoint, you should even rename the side-section to say "Legacy Twitch API v5 (Kraken)"
1 vote
- Don't see your idea?