Documentation still outdated for helix requirements
Even tho https://twitch.uservoice.com/forums/310213-developers/suggestions/40340764-add-client-id-headers-to-examples is marked as completed the docs are still 90% outta date for helix changes (According to Barry)
https://dev.twitch.tv/docs/api/guide#rate-limits still talks about not provided tokens
https://dev.twitch.tv/docs/api#step-2-sample-code still doesn't use a OAuth token
https://dev.twitch.tv/docs/api#step-3-results Is incorrect because step 2 doesn't use a OAuth token
8
votes
Dkamps18
shared this idea
-
julien_kay
commented
+1
But there are probably even more sections that are out of date.
-
BrandinArsenault
commented
There is a number of references in the Endpoints Section of the New Twitch API docs that suggests requests can be unauthenticated despite the new changes.