Extend the Videos API via a "metadata" endpoint, that provides additional data about the video.

Including but not limited to

• Category changes during the video
• Offsets are relative to the source video that the video is from. So for a highlight it would report the video it was cut from and include where in the origin file the highlight is cut from.

For Example: https://api.twitch.tv/helix/videos/metadata?id=1234
Metadata would support up to 100 (or 50) id's at once like Get Videos

Returns examples

A video of type archive
{
"data": [
{
"id": "1234",
"duration": 18000,
"chapters": [
{
"offset": 0,
"gameid": "200"
},
{
"offset": 500,
"gameid": "220"
}
],
parent: null
}
]
}

A video of type highlight
{
"data": [
{
"id": "1235",
"duration": 600,
"chapters": [
{
"offset": 300,
"game_id": "200"
}
],
"parent": {
"offset": 200,
"id": 4321
}
}
]
}

Use cases:

• if we present a highlight on a third party website, when the video is complete, we can present a easy way to go to the next Highlight in the series (where highlights are cut sequentially) or easily link to the original stream archive for continued watching.

This is an expansion of https://twitch.uservoice.com/forums/310213-developers/suggestions/38155990-return-tags-and-game-id-in-get-videos-in-helix

Brief description

https://dev.twitch.tv/docs/authentication/getting-tokens-oauth

When you get a token, it returns token_type as bearer

If you take this value as is and call helix endpoints it doesn't work as helix only accepts Bearer

How to reproduce

Generate a token
Construct a header using the returned data by concatenating elements from the returned JSON
`Authorization: ' . tokentype . ' ' . accesstoken

Call a helix endpoint
Get a 401
Expected behavior

Twitch accepts Bearer and bearer as valid

or

returns Bearer as the token type when fetching a token.

Additional context or questions

I'm not sure what the correct solutions is after a brief perusal of the RFC's

Request origin:

https://github.com/twitchdev/issues/issues/219

An update on Jan 31, 2019 gave channel moderators the ability to add comments to users within chat. There is currently no way to use the API to be able to set or retrieve comments for users in chat.

This should be available to the broadcaster and all moderators within a channel.

To add a mod comment to a user, the endpoint could take the following data as inputs:
- User: {user's name}
- Moderator: {mod's name}
- Broadcaster: {broadcaster's name}
- Comment: {comment to be applied}

On success, this would return the following:
- Success: {true}
- date: {date}
- User: {user's name}
- Moderator: {mod's name}
- Broadcaster: {broadcaster's name}
- Comment: {comment applied}

To retrieve mod comments of a user, the endpoint could take the following data as inputs:
- User: {user's name}
- Moderator: {mod's name (optional)}
- Broadcaster: {broadcaster's name}
- date: {date of comment (optional)}
- date range upper: {upper limit of date range (optional)}
- date range lower: {lower limit of date range (optional)}

On success, this would return the following for each comment:
- Success: {true}
- date: {date}
- User: {user's name}
- Moderator: {mod's name}
- Broadcaster: {broadcaster's name}
- Comment: {comment applied}

The new API endpoint 'Get User Follows'
https://dev.twitch.tv/docs/v5/reference/users#get-user-follows

Could include more data than what is currently provided.
The legacy endpoint alternative offers a lot more but not all of this info is required by default.
https://dev.twitch.tv/docs/api/reference#get-users-follows

My suggestion would be to at least provide the 'notifications' as well as the 'logo' info. To keep the requests at an optimal size by default, extra request parameters can be given such as:

?showLogo=true&showNotifications=true
(which can default to false when not present)

or

?verbose=true
(which will provide an equivalent response to the legacy variant)

The new endpoint should also only show this extra info as long as the token provided belongs to the given 'to_id'. Otherwise everyone can see who has the notifications activated for which streamer