Progress of a broadcast's template batch
Progress of the apply_template batch started by this API key's user on this broadcast, while it runs and for 10 minutes after its last update. 404 NO_ACTIVE_JOB when there is none, also once it aged out: the clips keep their templates either way.
apiKeyX-Api-Key<token>id*stringMonitor id, from GET /monitors
^[0-9]{1,19}$broadcastId*stringBroadcast id, from GET /monitors/{id}/broadcasts
Response for status 200
application/json- response
status*string"queued""processing""completed""failed"clips_count*numberClips in the batch
applied_count*numberClips that already have the template; their edit_id shows in the clip list
failed_count*numberfailed_ids*array<string>Clips the template could not be applied to. Send them again in clip_ids to retry
started_at*stringISO 8601
curl -X GET 'https://api.cut.pro/api/v1/monitors/string/broadcasts/string/clips/apply_template'{ "status": "queued", "clips_count": 0, "applied_count": 0, "failed_count": 0, "failed_ids": [ "string" ], "started_at": "string"}List clips of a broadcast GET
Returns the clips this workspace got from one broadcast, best rated first by default. While the broadcast is on air, new clips land every 10 minutes, so poll this list rather than waiting for the broadcast to end. A clip with an `edit_id` is ready to render or post; one without it renders with the default layout through `POST /monitors/{id}/broadcasts/{broadcastId}/clips/{clipId}/render`. Returns `410` once the recording was purged.
Apply template to broadcast clips POST
Applies one of your templates to every clip of a broadcast, or to the `clip_ids` given, in the background. Each clip's `edit_id` shows up in `GET /monitors/{id}/broadcasts/{broadcastId}/clips` as it is done. To template every future clip instead, set `template_id` on the monitor. Only one batch runs at a time per account: another one answers `429`.