Video captions take a public HTTPS URL; other media tools do not
Which URL each Sume video tool accepts: captions fetch a public HTTPS clip, while trim, filter, frames, inspect and timeline need your media.sume.com file.

When you chain Sume tools to make a vertical 1080x1920 file, the input rule changes at the caption step. Video captions takes a public HTTPS video_url that Sume can fetch. Video trim, video filter, video frames, video inspect and Timeline 1.0 take a media.sume.com artifact or asset that your workspace owns, and reject any other host at admit.
The lookup table
Every tool below returns a new durable file, except video frames and inspect, which return stills (and inspect also returns probe facts and optional text).
| Tool | Source URL it accepts | Output |
|---|---|---|
| video trim | media.sume.com file of your workspace | New MP4, up to 900 s |
| video filter | media.sume.com file of your workspace | New MP4, source up to 300 s |
| video frames | media.sume.com file of your workspace | Up to 24 stills |
| video inspect | media.sume.com file of your workspace | Probe, stills, optional transcript |
| Timeline 1.0 | media.sume.com files of your workspace | One MP4, default 1080x1920 |
| video captions | Public HTTPS URL Sume can fetch | Captioned video |
What captions refuses
The captions docs list the rejected URL kinds: localhost, private-network, non-HTTPS, signed or private URLs, and provider task URLs. A clip behind a signed bucket link therefore fails at the caption step even though it worked as input to trim. The captions docs example uses a media.sume.com/artifacts/... URL, which is the natural source when the previous step was a Sume tool, so the usual order is: trim and filter first, captions last.
A chain that respects the rules
Import once, then pass each step's result URL to the next. Put captions last so the burned text lands on the final 1080x1920 frame, and so the one caption job (fixed estimate $0.20 for clips of at most 60 seconds, confirm with GET /v1/catalog) sees the cut you will post.
Import the clip first with POST /v1/media-imports and send an Idempotency-Key on writes.
- Import:
POST /v1/media-importsreturns themedia.sume.comURL. - Cut:
POST /v1/video-trimwithstartandduration. - Crop and scale:
POST /v1/video-filter,scale=1080:1920,setsar=1. - Captions:
POST /v1/video-captionswith the resultvideo_url.
Errors you can hit
The two input rules fail in different ways, so read the error before you change anything. A Sume-hosted tool given an off-host URL such as https://example.com/clip.mp4 is rejected at admit, before a job exists; the fix is to import the clip. A Sume URL from another workspace or a dead link returns source_not_found. Captions given a private or signed link is rejected for that reason, and the fix is a public HTTPS URL or a Sume artifact URL.
Captions also have their own typed errors: caption_no_speech when speech-based captions find no speech (switch to cues), script_alignment_mismatch or script_alignment_failed when script_text cannot be aligned (simplify the script or omit it), and caption_hangul_text_latin_style when Korean text is sent to a Latin style. To change only the look, send source_caption_id in place of video_url; Sume reuses the stored word timings, so speech-to-text does not run again.
A note on order
The order matters for cost as well as for URLs. Trim and filter jobs are $0.02 each, and a caption job is a fixed $0.20 estimate for clips of up to 60 seconds, so do the cheap cuts first and caption only the final cut. A restyle through source_caption_id costs the same as a first caption job, so settle the framing before you burn text.
Sources
Related posts
More in Media tools
- Video captions rejects a signed URL: what to send instead
Sume video captions only fetches public HTTPS video URLs and rejects signed, private and localhost links. How to caption a clip that sits behind a signed link.
- Video filter 300 s source cap: trim a long clip first, then filter
Sume video filter rejects sources over 300 seconds while trim and detach take 1800. The output_duration_exceeded error, and a trim then filter order that fits.
- Dry-run a Sume video crop with video-filter check before a batch
POST /v1/video-filter/check validates a crop program without a job, credits or an encode. Run it first, then crop a batch of ad clips for new ratios.
- Video filter hdr_source_unsupported: what to do with an HDR clip
A Sume video filter job fails with hdr_source_unsupported on PQ or HLG clips. Why the filter refuses them, and three ways to get a usable result.
Written by Sume