...
| Endpoint | HTTP method | Purpose |
|---|---|---|
/api/catchup/v4/broadcast_slots/{channel_id} | GET | Get a list of catchup content available for a given channel. |
/api/catchup/v4/broadcast_slots/most_popular | GET | Get a list of the most watched catchup content available across all channels. |
Viewing Catchup per channel
...
The endpoint includes the series resources in the response, allowing for convenient grouping of the content by series.
Viewing most popular Catchup
A list of popular Catchup content across all channels can be retrieved using the most popular catchup endpoint. The endpoint returns the top 100 most watched Catchup content currently available. The popularity metrics are updated once per hour.
The series are included in the response, allowing for convenient grouping of the content by series.
Migration from legacy
The legacy endpoint /api/user/guest/recording/catchup/group and /api/user/guest/recording/catchup/group/<groupId> is replaced by the get catchup by channel endpoint.
The legacy endpoint /api/user/guest/recording/catchup/group with param sort=catcup_play_count_desc is replaced by the most popular catchup endpoint.
The endpoint returns the set of broadcast slots as well as their related series. The series objects can be used to implement the same type of grouping as was available from the legacy API.