Video analysis API with a YouTube link: 422 unsupported_source
Sume's video analyses reject YouTube URLs with 422 unsupported_source. Import the video you own to media.sume.com first; rules for the other bad inputs.

Sume's video analyses reject YouTube URLs with 422 unsupported_source. Pass a video you have the rights to as a durable media.sume.com URL, made with POST /v1/media-imports or taken from a finished Sume generation. Where creation is retired, use video inspect instead.
Which inputs does the analysis reject?
The video analyses docs list three unsupported cases. Only video_url is required, and the docs recommend a durable media.sume.com URL.
| Input | Result |
|---|---|
| YouTube URL | 422 unsupported_source |
| Non-HTTPS, private or localhost URL | Rejected at admit |
| A non-video asset | Fails with a stable, agent-legible code |
How do I get my own video in?
Import it. The docs prefer a durable media.sume.com URL from POST /v1/media-imports or a completed Sume generation artifact. Use only video you have the rights to. See Media inputs.
Does video inspect have the same rule?
Stricter. Video inspect reads only a clip already in your workspace on media.sume.com; off-host URLs such as https://example.com/... are rejected at admit. A dead or foreign media.sume.com URL fails as source_not_found.
curl -X POST https://api.sume.com/v1/video-inspect \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: inspect-import-001" \
-d '{ "video_url": "https://media.sume.com/artifacts/artf_demo/my-upload.mp4" }'Why not just fetch the link?
The inspect docs say there is no open-internet fetch: import first with POST /v1/media-imports, then pass the resulting media.sume.com URL.
Sources
Related posts
More in Developers
- Video API duration: whole seconds only, no 7.5 s clips
Sume's video duration is an integer and each model lists whole-second supported_durations. Ranges per model and how to pick one before you submit a job.
- Editing upload limits: Descript's GB tiers vs Sume's seconds caps
Descript lists per-file size caps by plan (1, 10, 20, 50 GB). Sume's media routes cap by clip duration instead: 300 s or 1800 s in, up to 900 s out.
- MCP tools for editing video: the hosted Sume list, trim to timeline
Descript and Runway both ship MCP servers. The hosted Sume MCP exposes video_trim, video_filter, audio_detach, video_frames_create and the timeline tools.
- video-filter order of operations: ops first, then filtergraph
In Sume video-filter, ops[] (dim, crop; max 8) run before the filtergraph, which has its own 2048-character and 32-filter caps. Order matters for a crop.
Written by Sume