Render and download the video

The clip the AI cuts is raw. The render turns the clip into a vertical MP4 with template, captions and effects, ready to post.

apply_template (optional)  →  POST .../render  →  GET /renders/{id}  →  GET /renders/{id}/download
        edit                    202 queued          until completed        1-hour URL

Apply a templateCopy Anchor Link

Templates are edits saved in Cut.Pro: framing, caption style, effects. List yours:

curl "https://api.cut.pro/api/v1/templates?filter=mine" \
  -H "X-Api-Key: $CUTPRO_API_KEY"

Each item carries id, name, aspect_ratio and auto_add_captions. filter=public lists Cut.Pro's.

To edit all of a submission's clips at once:

curl -X POST https://api.cut.pro/api/v1/clips/7412908365112823/submissions/7412908371004912/apply_template \
  -H "X-Api-Key: $CUTPRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "template_id": "7398110254410021", "clip_ids": ["7412908412887301"] }'

{ "clips_count": 1 }

Without clip_ids, it applies to all clips. It runs in the background: each clip gets an edit_id in GET .../clips when it finishes. One batch per account at a time; another responds 429 BATCH_ALREADY_RUNNING.

Simpler: send template_id already in POST /clips and every clip comes out edited.

Render a clipCopy Anchor Link

curl -X POST https://api.cut.pro/api/v1/clips/7412908365112823/submissions/7412908371004912/clips/7412908412887301/render \
  -H "X-Api-Key: $CUTPRO_API_KEY"

{
  "id": "7412910087712256",
  "edit_id": "7412910087700001",
  "status": "queued",
  "has_watermark": false,
  "output_resolution": "1080p",
  "from_cache": false,
  "download_url": null
}

With a template applied, the render uses the edit. Without a template, it uses the default layout. Keep the edit_id: it is what publishes the video and what generates a new file later.

If an identical render is already finished, the response is 200 with from_cache: true and download_url filled in. There is no queue and no waiting. Requesting the same clip while it renders responds 409 RENDER_ALREADY_IN_PROGRESS.

A live clip has its own route: POST /monitors/{id}/broadcasts/{broadcastId}/clips/{clipId}/render.

Follow the renderCopy Anchor Link

curl https://api.cut.pro/api/v1/renders/7412910087712256 \
  -H "X-Api-Key: $CUTPRO_API_KEY"

Poll every 5 to 10 seconds. progress goes from 0 to 100, handy for a progress bar.

Download the MP4Copy Anchor Link

curl https://api.cut.pro/api/v1/renders/7412910087712256/download \
  -H "X-Api-Key: $CUTPRO_API_KEY"

{ "url": "https://...", "filename": "The chorus everyone knows.mp4" }

Render againCopy Anchor Link

The edit never expires. To get the MP4 of a clip from months ago, render the edit_id:

curl -X POST https://api.cut.pro/api/v1/renders \
  -H "X-Api-Key: $CUTPRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "edit_id": "7412910087700001" }'

The edit_id of a render, a clip or a post item works. The response has the same format as rendering a clip.

Download several in a zipCopy Anchor Link

curl -X POST https://api.cut.pro/api/v1/renders/bulk-download \
  -H "X-Api-Key: $CUTPRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "render_ids": ["7412910087712256", "7412910087712257"] }'

curl https://api.cut.pro/api/v1/renders/bulk-download/$JOB_ID \
  -H "X-Api-Key: $CUTPRO_API_KEY"

• Up to 500 renders per zip. More than that responds 400 TOO_MANY_RENDERS.
• Ids from another workspace are ignored. If none are left, 404 NO_VALID_RENDERS.
• download_url appears in completed and is valid for 1 hour. The zip disappears at expires_at; after that, 410 JOB_EXPIRED.

List and deleteCopy Anchor Link

ErrorsCopy Anchor Link