Shutdown of the V5 API, great!, but

[Dere011]

@Dist

Anything that’s not already in Helix should not be expected to be in Helix when v5 is shutdown.

That’s why I posted my message, the lack of support for reruns is a big miss in the new API.

@Dist

If you want things added you’ll have to submit a feature request on UserVoice https://twitch.uservoice.com/forums/310213-developers or vote for existing ones for those suggestions.

It is already done, it is already sent for several years by other users. I have of course voted on the submissions in question.

@Dist

It’s also worth being aware of the Migration documentation as some things such as all of the Collections endpoints have already been marked No longer supported via the API.

Indeed, it is well noted for the collections. So I will inform my users about the stop of the related features.

@BarryCarlyon

ReRuns was filed as a GitHub here https://github.com/twitchdev/issues/issues/38 for tracking but may err towards a uservoice.

I had indeed seen this post on GitHub, but there is no update / news since

@BarryCarlyon

EventSub does report different “stream types” EventSub Subscription Types | Twitch Developers

But you can’t correltate this with a call to helix at the moment.

The EventSub allows you to retrieve this information, but as you say, without an API to correlate the information and above all to be able to check it periodically, it is totally unusable (at least for the features I propose).

@Dist @BarryCarlyon Thank you for your responses , I will make the necessary announcements and changes, hoping that support for reruns will return soon.