13 days after the Sora Videos API removal: the Sume /v1/videos route
OpenAI removed the Sora Videos API on September 24 with no replacement. What a team that still needs API video gets from Sume: submit, poll, download.
OpenAI lists the Sora Videos API removal for September 24, 2026 and names no replacement. If you still need video from an API, Sume offers an asynchronous /v1/videos route: submit, poll, download. It serves other vendors' models, not Sora, so prompts and durations must be re-tested rather than ported blindly.
What the OpenAI page says
The OpenAI deprecations page, read on October 7, shows the Sora Videos API with a removal date of September 24, 2026 and no recommended replacement. That makes today day 13 after the removal.
The Sume shape
The Videos docs describe four steps, and say the surface agrees field for field with the OpenRouter Video Generation API apart from a short list of differences.
| Step | Call | You get |
|---|---|---|
| Submit | POST /v1/videos | Job id and polling_url immediately |
| Poll | GET /v1/videos/{jobId} | status: pending, in_progress, completed, failed or cancelled |
| Download | GET /v1/videos/{jobId}/content | The mp4 once completed |
| Discover | GET /v1/videos/models | Resolutions, ratios, durations, audio and price per model |
What to re-test
Every catalog model has its own limits, so read them before you resubmit old prompts.
- Durations differ by model: seedance-2.5 takes 4 to 30 seconds, wan-3.0 takes 2 to 30, minimax-h3 takes 5 to 15, and gemini-omni-flash-1.1 takes 3 to 10.
- Sume uses bare model ids, with no provider prefix.
- Sume does not accept a size field on video; use resolution and aspect_ratio.
- A seed field is not on every model; check the seed flag in the model row.
Sources
Related posts
More in Developers
- A 429 from the Sume API: read budget, write budget or queue_full?
Three different 429s share a status. Read error.code and error.details.scope to tell read, write and queue_full apart, then retry each the right way.
- A lost response on a 30 s Kling motion control submit: reuse the key
If a network timeout hides the reply to a 30-second Kling motion control submit, a new Idempotency-Key reserves $4.725 again. Reuse the key. Python retry loop.
- Use your ad variant id as the Idempotency-Key on Sume
Name each ad variant once and send that name as the Idempotency-Key. Retries do not double-bill, and the receipt echoes it back so results map to your ad names.
- Add an object to a set spot in a photo: box to words in Python
Sume has no bounding-box field. Turn a 0-1000 box into placement words for an Ideogram 4.5 edit, and into pixels for a mask, with a short Python helper.
Written by Sume