Announcing the Latest Helix Endpoints and Hype Train API

@RAnders00
The documentation for the response was not updated, apologies for the confusion. status and description will be removed from the documentation, and game_name will be added. The example on the right is correct.

I will check on the intended empty value for game (null, empty string, etc)

You are correct about the 200 return code, this will be updated as well. It was a copy/paste error from the modify endpoint.

I will also check on how many broadcaster_ids can be specified and request this be added to the docs; both the maximum and the fact that multiple can be provided.

@WLG3R
Good catch, will pass that along to update the delete follow example.

@Six
Sorry for the confusion. status and description should not be documented as part of the get or modify channel information endpoints; these were removed during our beta process. User and Channel objects will not be consolidated, the intended differentiation is that a channel object contains the information about a channel page that belongs to a user while a user object contains information about the person.

@Hugo
Noted, the Get Stream Key formatting should be updated soon.

@tduva
Apologies for the confusion, this is an error. status and description will be removed.

@sogehige
I will double check with the team that only broadcasters are intended to have access through their oauth token or if editors should be allowed.

@moocat
Thanks for the reports. Passing both to the team.

@fiercekittenz
We’ll be sure to document more types should they become available, but yes, hypetrain.progression is the only one currently.

3 Likes