Restyle one captioned clip into three looks with source_caption_id
Pass source_caption_id to video-captions to re-burn the same clip in a new style without a second speech-to-text run. A restyle is still a billed render.

Send source_caption_id instead of video_url to POST /v1/video-captions. Sume reuses the first job's source video and its word timings, so no second speech-to-text runs, and you pick a different style or design. The docs are explicit that billing is unchanged: a restyle is still a render, so three looks is three renders, not one.
What changes and what does not
From the video captions docs: pass words alongside the id only to correct the wording. style accepts slam, punch, tiktok-green and others; design overrides colours, typography, placement, phrasing and motion, but is not supported on punch or tiktok-green.
| Item | Restyle with source_caption_id |
|---|---|
| Source video | Reused |
| Word timings | Reused, no second STT |
| Billing | Unchanged, still a render |
| design on punch or tiktok-green | Not supported |
Three looks
Keep the first job id, then submit a new job per look with a distinct Idempotency-Key. The docs list a fixed $0.20 per accepted standalone caption job for videos up to 60 seconds, so three looks of a short clip come to about $0.60 (confirm in GET /v1/catalog). Poll each job as described in Jobs and results.
curl -X POST https://api.sume.com/v1/video-captions \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: restyle-slam-001" \
-d '{
"source_caption_id": "vc_123",
"style": "slam",
"design": { "placement": { "anchor_ratio": 0.55 } }
}'Sources
Related posts
More in Media tools
- Roku ad frame rates: only three allowed, probe first
Roku ads reportedly accept 23.98, 25 or 29.97 fps. Probe your clip before upload with Sume's video inspect, and cut it to length if it is outside 6 to 92 s.
- Samsung Ads mobile video, 10 MB recommended: bitrate for 15 and 30 s
Samsung recommends 10 MB for mobile and tablet video, 30 MB for desktop. That caps a 30-second spot near 2.7 Mbps. The math, plus a Sume render and size check.
- Seedance 2.5 secondary edit vs trim-and-regenerate on Sume
BytePlus describes timestamp-level edits to Seedance 2.5 clips. Sume has no such edit field, so here is the trim-and-regenerate route and its limits.
- SeedVR2 10x video upscale vs Sume's upscale tool
SeedVR2 is listed with 1x to 10x video upscaling. Sume exposes a video_upscale_create tool, but its docs name no scale factors, so check the live schema first.
Written by Sume