Thank you! I just got the email.
A quick note - when JavaScript isn’t enabled, the examples become near impossible to read because the fallback colours for when syntax highlighting isn’t used are extremely similar: Background is #efeef1, while text colour is #dddddd. Here’s how that looks (from the “Get Users” endpoint docs):
This only occurs when JavaScript is disabled or not loaded from “static-elerium.cursecdn.com”; the syntax highlighting will work properly when this is enabled, so I recognise this probably isn’t a priority to fix, but I thought it might be worth pointing out!
Other things:
-
I’m a little confused as to what is meant by:
The new Twitch API uses the existing Twitch authentication system, and
it allows the use of application tokens for API calls. These application
tokens allow you to make an API request on behalf of your application
rather than on behalf of a user.When you say “the existing Twitch authentication system”, do you mean the same system as used in V5? I can’t see much information on the specifics used in this API.
-
Are other API endpoints planned in the future? It looks like there are only 5 endpoints in this version, which is a little worrying. (As far as I can see, there also appears to be no way to convert a
game_idfrom/helix/streamsinto a string of the game name, which I would consider essential functionality.)