Start monitoring
Turns monitoring on. For a live monitor, a channel that is already live starts being recorded within about a minute, and clips come from what airs from then on; nothing before the start is clipped. Calling it on a monitor that is already on changes nothing and answers 200. Refusals: 402, 403, 404.
Authorization
apiKey In: header
Path Parameters
^[0-9]{1,19}$Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/monitors/string/start"{ "id": "string", "type": "live", "platform": "youtube", "username": "string", "display_name": "string", "avatar_url": "string", "enabled": true, "enabled_at": "string", "strategy_id": "string", "template_id": "string", "video_min_duration": 0, "video_max_duration": 0, "days_of_week": [ 0 ], "hours_of_day": [ [ 0 ] ]}Stop watching a channel DELETE
Removes the monitor and turns it off. Clips it already produced stay in the workspace, and creating a monitor for the same channel and `type` again brings this one back with its history and automations, under the same `id`.
Stop monitoring POST
Turns monitoring off. No new batch is clipped or charged after this, and a recording in progress stops within about a minute. Monitoring must stay on for at least 10 minutes before it can be stopped: earlier you get `409` with `extra.remaining_seconds`. Calling it on a monitor that is already off changes nothing and answers `200`. Refusals: `404`, `409`.