Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dvr_api:deleting_recordings [2019/10/10 20:14] neds created |
dvr_api:deleting_recordings [2024/02/07 03:09] (current) neds [API URL] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Deleting recordings====== | ======Deleting recordings====== | ||
| + | <btn type="success" size="xs" icon="fa fa-chevron-left">[[:DVR API|Back to all DVR API topics]]</btn> | ||
| + | |||
| + | <WRAP center info> | ||
| + | This is a mirror of the documentation from: https://github.com/Silicondust/documentation/wiki/Deleting-Recordings | ||
| + | </WRAP> | ||
| A recording is deleted by sending a request to the record engine hosting the recording on the local network. The episode can optionally be flagged to be re-recorded. | A recording is deleted by sending a request to the record engine hosting the recording on the local network. The episode can optionally be flagged to be re-recorded. | ||
| Line 7: | Line 12: | ||
| The API URL is unique for each recording. Look for the "CmdURL" in the recorded files json from the record engine. Note that the CmdURL may include parameters which must be preserved. | The API URL is unique for each recording. Look for the "CmdURL" in the recorded files json from the record engine. Note that the CmdURL may include parameters which must be preserved. | ||
| + | |||
| + | The API URL must be invoked using a HTTP POST operation. HTTP GET operations will be rejected with 400 Bad Request. | ||
| </WRAP> | </WRAP> | ||
| Line 27: | Line 34: | ||
| </WRAP> | </WRAP> | ||
| + | ====History==== | ||
| + | <WRAP indent> | ||
| + | |||
| + | * 20210804: | ||
| + | * Document requirement to use HTTP POST. | ||
| + | |||
| + | * 20160427: | ||
| + | * Initial documentation. | ||
| + | |||
| + | </WRAP> | ||
| + | Copyright © 2016 Silicondust USA Inc. <www.silicondust.com>. | ||