Twitch isn’t maintaining a list of API bugs, and the Github Issues isn’t organized. Someone mentioned there wasn’t a list of known API issues, so here’s a list to the best of my knowledge. I’ll try to keep it updated, and if I’m missing something let me know.
- Wrong API version being served
- If you request version 3 of
/users/:user
, for some users you might be served version 2. This is confirmed to be a caching issue with no known ETA on a fix.
- If you request version 3 of
- Wrong channel subdocument served inside a stream object
- Some requests to
/streams
may result in the channel object being the object of the user instead. - In some rare instances, I believe a different user may have been served.
- This is another caching issue with no known ETA on a fix.
- Some requests to
- You cannot use the query string parameter “client_id” on
/streams
- This is because some streaming clients use the Twitch API and have a
client_id
.
- This is because some streaming clients use the Twitch API and have a
- You can only request the first and last 1600 followers of a channel.
- Due to excessive server load caused applications scraping lists of followers, Twitch has decided to limit the amount of followers you can offset.
- Twitch is working on a solution, but it has been proposed that an implementation similar to Twitter’s might be implemented. In this implementation a cursor would be used to allow you to move forwards and backwards through a list, most likely using previous and next links inside the
_links
key provided in the API response.
- For new Twitch channels,
mature
is “null” instead of false in the channel object.- Since
mature
is a boolean, it should default to false.
- Since
-
/search/streams
returns valid_total
count, but is missing some streams in the response- Instead of 10 results being returned, less than 10 are returned for each page.
- Example: https://api.twitch.tv/kraken/search/streams?q=starcraft
- Non-SSL resources are linked in an SSL-only API.
- Twitch image resources support SSL, so just replace
http://
withhttps://
- Video player embed does not work on SSL websites
- Twitch chat embed does not work on SSL websites
- Twitch image resources support SSL, so just replace
- There’s no way to get members of a team in the Kraken Twitch API.
- You can use the old teams API until a replacement happens.
http://api.twitch.tv/api/team/:team_name/all_channels.json
- “Don’t allow other users to embed your videos” only works for VoDs
- I think access control is a big deal for certain streamers. Twitch should better honor this setting to keep content on the actual Twitch website.
- OAuth implementation breaks RFC in certain instances (not really a big deal)
- Should be using Authorization “Bearer” header
- Should be using “access_token” query string parameter
- Should allow clients to revoke access tokens
- During high peak hours, API OAuth authentication codes and access tokens not immediately active
- These codes and tokens usually become active after some seconds of waiting.
- I retry an access token multiple times before giving up, which might work for you too.
- Auth Code Flow assigning incorrect scopes and not properly revocating tokens
- Access tokens may not be revoked when a user “disconnects” an application on the Twitch website or reauthenticates with your application.
-
Some users may not be able to get the required scopes to use your application, see Scope 'user_read' not working for explanation- fixed™ - This could not be reproduced using the implicit auth flow