Stop monitoring
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.
apiKeyX-Api-Key<token>id*stringMonitor id, from GET /monitors
^[0-9]{1,19}$Response for status 200
application/json- response
id*stringMonitor id, used in every /monitors/{id} route
platform*string"youtube""twitch""kick"username*stringChannel handle on the platform
display_name*||Channel name as shown on the platform
avatar_url*string|null|nullenabled*booleantrue while the monitor is on. It can also turn itself off when the balance runs out
enabled_at*||ISO 8601 timestamp of when the current monitoring period started; null while off. Stopping is refused for the first 10 minutes after it.
strategy_id*stringClipping strategy applied to every clip
template_id*||Edit template applied to every clip; null = none
type*"live""live"on_air*booleantrue while the channel is broadcasting
broadcasts_count*numberBroadcasts recorded since the channel was first monitored
clips_count*numberClips this workspace got from the channel's broadcasts whose recording is still kept
last_broadcast_at*||ISO 8601 timestamp of when the latest broadcast started
thumbnail_url*||Cover of the latest broadcast. Signed URL, time-limited
next_batch*||Progress of the next batch; null unless the broadcast is on air and the monitor is on
batch_credits*numberCredits the next 10-minute batch of this channel costs your workspace, after any discount
curl -X POST 'https://api.cut.pro/api/v1/monitors/string/stop'{ "id": "string", "platform": "youtube", "username": "string", "display_name": null, "avatar_url": null, "enabled": true, "enabled_at": null, "strategy_id": "string", "template_id": null, "type": "live", "on_air": true, "broadcasts_count": 0, "clips_count": 0, "last_broadcast_at": null, "thumbnail_url": null, "next_batch": null, "batch_credits": 0}Start monitoring POST
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`.
List broadcasts of a live monitor GET
Returns the channel's broadcasts, newest first, each with how many clips this workspace got from it. A broadcast with `ended_at: null` is on air and keeps producing clips every 10 minutes while the monitor is on. Only `live` monitors have broadcasts: a `video` monitor answers `400 INVALID_OBSERVING_TYPE`, and its clips arrive as regular submissions in `GET /videos`.