Cafiyn Pulse
← Startup Signals
4 min readUpdated 2026-09-07Issue 2

The Videos API goes away on 24 September and OpenAI names nothing to move to.

Every other deprecation on OpenAI's page offers a migration target. This one does not, which makes it a different kind of problem.

ByKarthik KumarCafiyn Innovations
At a glance
Removal date
24 September 2026
Announced
24 March 2026, six months notice
Affected
Videos API, sora-2, sora-2-pro and snapshots
Named replacement
None

What is being removed

OpenAI notified developers on 24 March 2026 that the Videos API, along with the sora-2 and sora-2-pro model aliases and their snapshots, would be removed from the API on 24 September 2026. The deprecation entry lists no successor model or endpoint.

That absence is the whole story. Look down the rest of the deprecations page and every entry pairs a shutdown with a migration: the reasoning models point at the GPT-5.6 family, the image models point at gpt-image-2, the transcription models point at gpt-transcribe. This one points nowhere.

Why a missing replacement changes the work

A deprecation with a named successor is usually a string change plus a regression test. You swap the model identifier, re-run your evaluations, check that output shape and latency are close enough, and ship. The work is bounded and you can estimate it.

A deprecation with no successor is a vendor selection exercise. You have to survey what else exists, test output quality against your actual prompts rather than a demo, compare pricing models that may not be shaped the same way, check terms for your use case, and then do the integration. That is a different order of work, and it cannot be compressed into the week before the deadline.

As of publication that leaves seventeen days. If video generation is a feature your users can reach, this is the item on the calendar to deal with first, ahead of things with later dates but easier migrations.

What to check

The endpoint and the model names are both greppable, and the surface area is usually small because video generation tends to be one feature rather than a cross-cutting dependency.

  • Grep for sora-2, sora-2-pro and any pinned snapshot identifiers
  • Grep for the videos endpoint path in your API client code
  • Check whether video generation is exposed to users or only used internally, which changes the urgency
  • If it is user-facing, decide now whether to replace the provider or remove the feature, because both take longer than a model swap

What to do

  1. 1Grep for sora-2 and the videos endpoint today. Seventeen days is enough time to change vendor, but not much more.
  2. 2Decide explicitly between replacing the provider and retiring the feature. Drifting into the deadline chooses the second option for you.
  3. 3If you replace, test against your real prompts rather than the vendor's samples: video quality varies far more by prompt than text does.
  4. 4Check your terms and content policy against the new provider, which is easy to skip and awkward to discover later.

Common questions

When exactly is the Videos API removed?

24 September 2026. OpenAI notified developers on 24 March 2026, giving six months notice.

What does OpenAI recommend migrating to?

Nothing. The deprecation entry names no replacement, which is unusual on that page and is what makes this a vendor-selection problem rather than a model swap.

Which models are affected?

The Videos API itself, plus the sora-2 and sora-2-pro aliases and their pinned snapshots.

Sources

Read against the primary documentation rather than secondary coverage. Where a figure comes from a provider's own docs, it is quoted as published on 2026-09-07.

Related

More from Signals

OpenAI has published seven shutdown dates. Here is the calendar.
Seven dates between 23 October and 26 February. Every one announced months ahead, in public. The failure mode is never the notice.
Nvidia bought Hugging Face. Your open-weight fallback is now a vendor relationship.
The commitments say nothing breaks. The structural change is that "we can always self-host" is now a dependency on one vendor rather than on a neutral commons.
Whisper shuts down on 26 February. The risk is not the deadline.
Five months is a generous window. Whisper is also typically wired into a background job that fails into a queue rather than into a user's face.
The Assistants API is gone. Your app may not have told you yet.
It shut down on 26 August 2026. The replacement is not a drop-in, and the most common migration mistake changes your model's behaviour without throwing an error.
One Copilot code review costs 13 requests. Here is the rest of the maths.
Copilot now bills on usage rather than seats. The headline change is simple. The multipliers underneath it are where teams get surprised.
Row-level security is on by default now. That is not the same as being protected.
Lovable fixed the default. The gap that actually leaks data was never the default, it was the policy, and no platform can write that for you.
Your model comparison is measuring the wrong number.
Every price list is per token. Your bill is per finished piece of work. Those two numbers can rank models in opposite orders.
An agent with production log access is a new identity. Treat it like one.
Always-on agents that read production logs are arriving fast. The access-control question they raise is old and well understood, which is the good news.

Open the tool.

Ten production categories, three minutes, and a ranked list of what to fix first.

Check your own stack