> ## Documentation Index > Fetch the complete documentation index at: https://cut.pro/docs/llms.txt > Use this file to discover all available pages before exploring further. # Apply template to clips > 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. ## OpenAPI ````yaml https://api.cut.pro/api/v1/openapi.json post /clips/{videoId}/submissions/{submissionId}/apply_template openapi: 3.0.3 info: title: CutPro API version: 1.0.0 description: >- The CutPro API lets you automate AI-powered video clipping and rendering programmatically. ## Typical workflow 1. **Analyze** a public video URL to preview metadata and credit cost — no charge (`POST /clips/info`) 2. **Submit** the video for AI clipping — credits are deducted immediately (`POST /clips`) 3. **Poll** the submission until `status` is `completed` or `failed` (`GET /clips/{videoId}/submissions/{submissionId}`) 4. **Fetch** the AI-generated highlight clips (`GET /clips/{videoId}/submissions/{submissionId}/clips`) 5. **Optionally** apply one of your templates in bulk (`POST /clips/{videoId}/submissions/{submissionId}/apply_template`) 6. **Render** each clip to a final MP4 (`POST /clips/{videoId}/submissions/{submissionId}/clips/{clipId}/render`) 7. **Poll** the render until `status` is `completed` (`GET /renders/{renderId}`) 8. **Download** the rendered video (`GET /renders/{renderId}/download`) ## Authentication Pass your API key on every request via the `X-Api-Key` header or as `Authorization: Bearer `. You can generate API keys from your account settings at [cut.pro](https://cut.pro). ## Workspaces An API key is bound to one or more workspaces (Cloudflare-style scoped tokens). - **Single-workspace key**: every request operates on that workspace automatically. No header needed. - **Multi-workspace key**: pass `X-Workspace-Id: ` on every request to pick which workspace the call hits. Without the header, you get `400 MISSING_WORKSPACE_ID` with the list of allowed workspace ids in the response. Call `GET /workspace` to inspect the workspace the current request resolved to, plus its plan and role. ## Credits Credits are consumed when a submission is created. Check the workspace balance at `GET /balance`. Use `POST /clips/info` to see the exact cost before committing. servers: - url: https://api.cut.pro/api/v1 security: [] tags: - name: Workspace description: >- The workspace this request resolved to. Single-workspace keys always resolve to their bound workspace. Multi-workspace keys resolve via the `X-Workspace-Id` header — credits, submissions, clips and renders belong to whichever workspace the header selects on each request. - name: Videos description: >- Your clipping library — the source videos you have submitted for AI clipping. - name: Submissions description: >- Clipping jobs — the full lifecycle from pre-flight analysis through AI processing to completion. Each submission is tied to a video and produces a set of generated clips when it completes. - name: Clips description: >- AI-generated highlight clips produced by a completed submission. Each clip includes timestamps, a relevance score, and signed URLs for streaming and downloading. Clips can have a template applied and then be rendered to a final MP4. - name: Renders description: >- Video render jobs. After optionally applying a template to a clip, start a render to produce a final MP4. Poll the render until completed, then download the file. - name: Posts description: >- Multi-platform publishing. Create a post that references one or more edited clips plus the social connections to publish to, then poll it through `pending → processing → completed`. Failed items can be retried or removed without disturbing siblings that already published. - name: Templates description: >- Video editing templates that apply visual effects, captions, cropping, and other styles to clips in bulk. List your templates to find an ID to pass to `apply_template`. - name: Balance description: >- Credit balance and ledger of the workspace this API key represents. Credits are consumed when you create a submission. For full workspace metadata (plan, seats, role, member count) see `GET /workspace`. - name: Connections description: >- Social media accounts connected to this workspace — the IDs you pass as `connection_id` when creating a post. To connect a new account, sign in at [cut.pro](https://cut.pro) and use the in-app OAuth flow; connection lifecycle is not exposed via API. paths: /clips/{videoId}/submissions/{submissionId}/apply_template: post: tags: - Clips summary: Apply template to clips description: >- 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. operationId: applyTemplate parameters: - name: videoId in: path required: true schema: type: string - name: submissionId in: path required: true schema: type: string requestBody: required: true content: application/json: schema: type: object required: - template_id properties: template_id: description: >- ID of the template to apply — must be one of your own templates (see `GET /templates`) type: string clip_ids: description: >- Subset of clip IDs to apply the template to. Omit to apply to all clips in the submission type: array items: type: string application/x-www-form-urlencoded: schema: type: object required: - template_id properties: template_id: description: >- ID of the template to apply — must be one of your own templates (see `GET /templates`) type: string clip_ids: description: >- Subset of clip IDs to apply the template to. Omit to apply to all clips in the submission type: array items: type: string multipart/form-data: schema: type: object required: - template_id properties: template_id: description: >- ID of the template to apply — must be one of your own templates (see `GET /templates`) type: string clip_ids: description: >- Subset of clip IDs to apply the template to. Omit to apply to all clips in the submission type: array items: type: string responses: '200': description: Response for status 200 content: application/json: schema: type: object required: - total properties: total: description: 0 — no clips matched the filter type: number '202': description: Response for status 202 content: application/json: schema: type: object required: - total properties: total: description: Number of clips the template is being applied to type: number '404': description: Response for status 404 content: application/json: schema: type: object required: - code properties: code: type: string enum: - SUBMISSION_NOT_FOUND - TEMPLATE_NOT_FOUND '429': description: Response for status 429 content: application/json: schema: type: object required: - code properties: code: type: string enum: - BATCH_ALREADY_RUNNING security: - apiKey: [] components: securitySchemes: apiKey: type: apiKey in: header name: X-Api-Key ````