Video analyses API returns 410 video_analysis_retired: fix
POST /v1/video-analyses answers 410 video_analysis_retired in Sume's dest environment. Stored rows stay readable; new clip inspection uses video inspect.

If POST /v1/video-analyses returns 410 video_analysis_retired, you are calling Sume's dest environment, where creating an analysis is switched off. It is not a production outage. Move new work to POST /v1/video-inspect, which the docs name as the default clip inspection on dest and prod.
Why do I get a 410?
The video analyses docs say create is retired on dest, and that production keeps accepting it for now. MCP wrappers named video-analyses_* are also delisted from the tool list on dest. The page tells you not to start new work on this surface.
Can I still read old analyses?
Yes. Stored vana_ rows stay readable through GET /v1/video-analyses/:id and GET /v1/video-analyses in both environments, so existing results are not lost.
| Call | Dest environment | Production |
|---|---|---|
| POST /v1/video-analyses | 410 video_analysis_retired | Still accepted until retirement |
| GET /v1/video-analyses/:id | Reads stored rows | Reads stored rows |
| GET /v1/video-analyses | Lists stored rows | Lists stored rows |
What do I use instead?
Video inspect probes one media.sume.com clip, samples stills and can transcribe. Probe and stills are unbilled; the default is mode: sync, which waits up to 30 seconds. It does not return typed scenes, so it is not a drop-in swap for scenes[].
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-migrate-001" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/ad.mp4",
"frames": { "fps": 1 }
}'What if I need semantic questions about the video?
The docs mention video_analyze and video_segment on dest only when those names appear in the tool list, and say they are not for production. Check the tool list rather than assuming they exist.
Sources
Related posts
More in Developers
- Video analysis limits: max_scenes 2-40 and the 90 s and 300 s caps
Sume's video analysis takes max_scenes from 2 to 40 (default 24), warns past about 90 seconds and rejects past 300. Cost, runtime and polling advice.
- What a Sume video analysis returns for each scene
Each scene in a stored video analysis has start and end seconds, summary, visual, shot type, on-screen text, confidence and keyframes. Field-by-field list.
- 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.
- 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.
Written by Sume