...
Endpoint | HTTP method | Purpose |
---|---|---|
/api/recordings/v4/user_profiles/{user_profile_id}/recordings/recording_groups | GET | See all recording groups |
/api/recordings/v4/user_profiles/{user_profile_id}/recordings/recording_groups/{recording_group_id}/recordings | GET | See all recordings in a group (Deprecated) |
/api/recordings/v4/user_profiles/{user_profile_id}/recordings/recording_groups/ungrouped/recordings | GET | See all recordings not in any group (Deprecated) |
Recordings are automatically grouped by series by default or grouped by series_id|channel_id with optional parameter. The client can obtain a list of recording groups available to their profile by calling the recording groups endpoint.
The contents of each group can be viewed by calling the get grouped recordings endpoint. For recordings that do not belong to any group, the special ungrouped endpoint can be used. These two endpoints will always include the related broadcast slots in the response, that contain information about the contents of the recording to be shown to the user.
The client can filter the output of these APIs the API by favourite, starts_before, starts_after, ends_before, ends_after.
Automated recording
Info |
---|
"Automated recording" feature replaces the feature previously known as "Continuous recording". |
...
Info |
---|
Automated recordings are only rules for the system to automatically keep adding recordings to the particular series along they get populated to the channel's program schedule. This means that the user's recording quota is not taken into account when adding the automated recording request. The automated recording request will keep on running as a background process if the user's recording quota allows it. If the quota gets full, the process will not add new recordings anymore. Respectively when some quota is freed, the process will continue adding the automated recordings based on the user's stored automated recording rules. |
Postman collection
View file | ||||
---|---|---|---|---|
|