Sora's API shuts down today. Vendors delete features.

The Sora API stops answering today. OpenAI's deprecations page lists the Videos API and every Sora 2 alias — sora-2, sora-2-pro, and the dated snapshots — as announced on March 24, 2026 and removed on September 24, 2026. The recommended-replacement column is a dash. If you shipped video generation on the Sora API, your pipeline breaks at some point in the next 24 hours, and there is no drop-in successor at the same vendor.

What actually happened

OpenAI announced the shutdown in March, roughly six months after the Sora app launched. TechCrunch and CNN covered it the day it was announced. The consumer app and web experience went dark on April 26. The API got a longer runway and lands today.

The company's stated reason was focus: the Sora research team is moving toward world-simulation work aimed at robotics. Reporting at the time also pointed at compute pressure and unresolved likeness and copyright problems. We're not going to put a number on what Sora cost to run — the figures circulating come from secondary write-ups, not from OpenAI.

What matters for builders is the shape of the notice, not the motive. Two dates, six months apart, published on a docs page. That is a well-run deprecation by industry standards. It still ends with your feature gone.

Why API deprecation matters for your business

Every AI feature you ship has a half-life you don't control. Sora is not an outlier — it's the normal case with a clean paper trail.

The mistake we see most: the model ID is hardcoded in three services, the outputs live only in the vendor's storage, and nobody wrote down which customer-facing feature depends on which endpoint. When the email arrives, that team spends a week doing archaeology before they can start the actual migration.

The fix is boring and takes an afternoon.

Put a seam in front of every model call. One internal function — generateVideo(prompt, opts) — with the provider behind it. Model IDs and endpoints live in config, not in code. Swapping Sora for Runway, Veo, or a self-hosted model becomes a config change plus an eval run, not a refactor.

Store the outputs yourself. Render to your own S3 or R2 bucket the moment a job completes. Vendor-hosted assets disappear on the vendor's schedule. Sora users were told to export from a sunset page — don't be in that position for your customers' assets.

Keep a dependency map. A flat file listing every external model, the feature it powers, and who owns it. When a deprecation notice lands, that file turns a scramble into a ticket.

Subscribe to the deprecation page, not the newsletter. OpenAI, Anthropic, and Google all publish machine-readable deprecation schedules. Six months is plenty of notice — if someone is reading it.

Sources: OpenAI API deprecations, TechCrunch, CNN Business.