video_url 400 on Sume: edit is supported only by Omni Flash 1.1
A video_url on any other model returns 400 on the Sume Video Router. Which models take a source video, and how to pick one for your edit.

The error says video_url (edit) is supported only by model gemini-omni-flash-1.1. It means you sent a prompt-driven edit to a model that has no edit mode. On the Sume Video Router, only gemini-omni-flash-1.1 rewrites a clip from a prompt. Other video-in routes exist, but they use different fields and do different jobs.
Fields that look alike
| Field | Model | What it does |
|---|---|---|
| video_url (edit) | gemini-omni-flash-1.1 | Applies the prompt to your clip |
| video_url + reference_image_urls | higgsfield-genjutsu | Motion transfer onto 1 to 8 reference images |
| video_url + reference_image_urls | h3-max-recast | Swaps people in the source for 1 to 4 photos |
| reference_video_urls | models that list video references | Guides a new clip; not an edit of yours |
How to fix the call
Decide whether you want to change a clip or create a new one inspired by it. Changing: use Omni Flash edit with a source of 10 seconds or less. Person swap or motion transfer: use the model built for it. New clip guided by footage: use reference_video_urls on a model that lists them, and check the model list first.
Also note the error on mixing fields: a video_url edit cannot carry frame or reference fields in the same request.
Sources
Related posts
More in Developers
- Virtual try-on API: which Sume call returns an image, which a video
Need a try-on photo or a try-on clip? On Sume the two catalog try-on Formats return video; a still comes from the image API. The table, plus one call for each.
- Unit-test a Sume submit-and-poll loop in Vitest with fake replies
Test a Sume polling loop without spending credits: inject the sleep, replay queued then completed replies, and assert next_poll_after_seconds is honored.
- Test a webhook endpoint before go-live: a Sume CI gate (Python)
Use POST /v1/webhooks/test-deliveries to fire a signed webhook.test at your deployed URL and fail the deploy unless it answers 2xx. Python script included.
- What to measure for Sume API jobs: metrics, labels and alerts
A metrics plan for code that calls the Sume API: submit outcome, queue wait, time to terminal, error code and webhook gap, with low-cardinality labels.
Written by Sume