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.

4 min readSume
All posts

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.

Unsupported analysis inputs, read 2026-09-30 from the Sume docs.
InputResult
YouTube URL422 unsupported_source
Non-HTTPS, private or localhost URLRejected at admit
A non-video assetFails 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

All Developers posts

Written by Sume