24 results found
-
Extra info regarding requesting access_tokens With the new changes to require OAuth tokens for every request; I think it would be useful to talk about how many times one should and could request tokens.
The easiest path upgrading a legacy implementation is just requesting an access_token on every call. After reading the docs I can't make a good guess whether a low-traffic application can use this approach.Thanks!
1 vote -
Outdated API reference to get channel ID It seems the API being referenced to determine a "channel id" is out of date, "<channel ID> is the _id field returned by the Twitch API v5 Get Channel endpoint."
As I receive the following when attempting to acquire metadata via my client-id at the mentioned API:
{
"message" : "The API version you are looking for is in another castle. See https://dev.twitch.tv/docs",
"error" : "Gone",
"status" : 410
}I'm finding it incredibly confusing understanding where my channel-id comes from. Is it also my user-id? broadcaster-id?
1 vote -
Don't tell people to auth in a non-standard way Make the docs closer to OAuth specs. The docs say to send parameters to /token (and /revoke) in the query string, but this is non-standard. Twitch supports the parameters in either the query string or request body.
The documentation should prefer the standard approach of sending parameters in the request body.
4 votes -
Twitch authentication code samples https://dev.twitch.tv/docs/authentication
"Code samples are available here."
This line needs to be updated to point to different examples as the repo has been updated, for example for nodejs example its now at:
https://github.com/twitchdev/authentication-node-sample
not sure why someone decided it made sense to separate examples rather than place them in one repo
1 voteThank you! We’ve updated the links.
- Don't see your idea?