The new Twitch API docs are live

[Dist]

@Sophira

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.

The current v5 authentication remains, but from my understanding there is now more of a reason to use app access tokens as as the new docs mentions:

Each client ID is granted a total of 30 queries per minute (if an OAuth token is not provided) or 120 queries per minute (if an OAuth token is provided), across all new Twitch API queries. If this limit is exceeded, an error is returned: HTTP 429 (Too Many Requests).

Which if I understand correctly means that if we had an app that for example is needing data on thousands of users, then using an app access token in this case would allow for 120 queries/min.

@Sophira

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_id from /helix/streams into a string of the game name, which I would consider essential functionality.)

If you check out the Roadmap they have the games API (and several others) in their ‘exploring’ section. So it is reasonable to assume that translating a game_id to game name will be coming, but might be some ways off.