Hi all,
I’m having a little bit of a concern here and hoping someone can correct me.
At present my application utilises Kraken V5 API, I’m looking to move to Helix if I’m honest before the deprecated API is given a death date and I’m forced to run around mad.
At present, some of my users have their profile information displayed on the application, simple, public facing information:
- Profile Picture - https://dev.twitch.tv/docs/v5/reference/users#get-user-by-id (Using ID retrieved by another Kraken API callback https://api.twitch.tv/kraken/users?login={Username})
- Bio - https://dev.twitch.tv/docs/v5/reference/users#get-user-by-id
- Most Recent Clips - https://dev.twitch.tv/docs/v5/reference/clips#get-top-clips
I’ve came across one small issue and I’m hoping it’s just me misreading the documentation somewhere. I’ve actively requested a App Access Token in order to access the public facing information from the Helix API, most of which I can pull again at ease
- Profile Picture - https://dev.twitch.tv/docs/api/reference#search-channels
- Clips - https://dev.twitch.tv/docs/api/reference#get-clips
- Bio - ???
My concern is I can no longer get the public facing bio of a channel unless they provide OAuth and since then the key of bio has been renamed to description (https://dev.twitch.tv/docs/api/reference#get-users)
Is this now intended? That we cannot retrieve their public facing channel description without getting them to authorize the application with the ‘user:read:email’ scope ?
I feel if that is the case it’s a little overly restrictive when it could be placed into search channels API, perhaps a suggestion? The application doesn’t require any, at present, authenticated actions or access to view sensitive data such as sub counts etc, just simply public facing information that I can proactively seen on their channel intially anyway.
Perhaps I’m looking in the wrong place, a little clarification would go a long way
Thanks folks!