Progress of a submission's template batch
Progress of the apply_template batch started by this API key's user on this submission, 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>videoId*stringVideo id, from POST /videos/info or GET /videos
submissionId*stringSubmission id, from GET /videos/{videoId}/submissions
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/videos/string/submissions/string/apply_template'{ "status": "queued", "clips_count": 0, "applied_count": 0, "failed_count": 0, "failed_ids": [ "string" ], "started_at": "string"}Retry a failed submission POST
Runs a `failed` submission again with the exact settings it was created with (strategy, timeframe, template, translation) and returns the NEW submission, charged like `POST /videos/{videoId}/submissions`. The failed one stays in the history. Retrying a submission that did not fail answers `409 SUBMISSION_NOT_FAILED`.
Apply template to clips POST
Asynchronously applies one of your saved templates to all (or a subset of) the generated clips in a submission. The job runs in the background: returns immediately with the number of clips being processed. Once a template is applied, each clip gets its own edit settings that you can then render via `POST /videos/{videoId}/submissions/{submissionId}/clips/{clipId}/render`. Only one batch job can run at a time per account. Returns `429` if another is already running.