Sora, Veo and Omni preview shutdown dates in one table (Oct 2026)

OpenAI's deprecations page says it notified developers on March 24, 2026 that the Videos API and the Sora 2 aliases and snapshots would be removed on September 24, 2026, and it names no replacement (OpenAI deprecations, read 2026-10-09). Google's page lists three Veo 3.1 preview ids and gemini-omni-flash-preview for shutdown on October 22, 2026, with gemini-omni-1.1-flash as the replacement (Google deprecations, read 2026-10-09).

What is the full dated list?

Which of these affects a Sume integration?

Sume uses its own bare catalog ids and lists none of the retired ones. Its Omni row is gemini-omni-flash-1.1, and the docs state the Sume contract never carries a provider-org prefix. A request that still sends sora-2 or a Veo id will not match a catalog model. Sume also says it will retire its own Video 1.0 alias soon, which maps to Auto; new code should use POST /v1/videos.

How do you stop a retirement surprising you?

The video generation docs describe the models endpoint, and the Video Router docs show the catalog fields.

• Read GET /v1/videos/models in CI and fail the build if a pinned id is missing.
• Keep one config value for the model id, not a literal in each call.
• Log the model field from each job so you can see which id served it.
• Check each vendor's deprecations page on a schedule, and note the date you read it.

What about Omni itself?

Google lists no shutdown date for gemini-omni-1.1-flash. That is not a promise, so pin the id and re-read the page before large campaigns.