Delete submission
Permanently deletes a submission and all its generated clips. This action cannot be undone. Returns 409 if the submission is currently processing — wait for it to complete or fail first.
Authorization
apiKey In: header
Path Parameters
Response Body
application/json
application/json
application/json
curl -X DELETE "https://example.com/clips/string/submissions/string"Get submission GET
Returns the current status of a clipping submission. Poll this endpoint until `status` is `completed` or `failed`. We recommend polling every **5–10 seconds**. When `status` is `queued`, use `queue_position` and `estimated_time` to give feedback to your users. A submission can sit at `downloading` because the SOURCE is not fully published yet — a scheduled premiere, a livestream still on air, or a recording the platform is still processing. In that case `waiting_reason` is set (and `waiting_until` carries the announced start time, when the platform provides one). This is not an error and the submission is not stuck: it resumes on its own once the source becomes available. Surface it to your users instead of a generic "downloading", and offer them the option to cancel — `DELETE /v1/clips/{videoId}/submissions/{submissionId}` refunds the credits while `waiting_reason` is set.
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 /clips/{videoId}/submissions/{submissionId}/clips/{clipId}/render`. Only one batch job can run at a time per account. Returns `429` if another is already running.