Sora 2 Discontinued? 2026 Shutdown Date, Background and the Best Sora Alternatives

Is Sora 2 discontinued?

For API users, the answer is yes. OpenAI’s published schedule separates two events: the consumer Sora experience ended on April 26, 2026, and the Sora API plus Sora 2 models ended on September 24, 2026. OpenAI notified affected developers on March 24, 2026. The dates are easy to mix up because “Sora discontinued” can refer to the app, the API, or a third-party gateway.

For APIMaster, the retirement is independently verifiable. The marketplace metadata removal was committed on September 28, 2026, and the Sora documentation pages were removed and redirected shortly afterward. The current API data has no status=1 route for either Sora model.

Why does a Sora page still exist?

A page is not a route. Search indexes, model directories, cached docs, OpenRouter history, and SDK enums often outlive the provider connection. A page can still contain the old model ID, old pricing, or an example request while the gateway returns no available channel.

Use three checks before treating a video model as usable:

1. Is there a current official API model ID and documentation?
2. Does the gateway show at least one active route or endpoint?
3. Does a minimal request create a task with current pricing and limits?

Sora 2 fails the second check on APIMaster as of October 5, 2026. That is why this page calls the old prices historical references rather than current APIMaster prices.

What caused the Sora shutdown?

The confirmed background is the official discontinuation schedule and the resulting route removal. The public notices do not establish one specific technical or commercial cause such as cost, licensing, policy, capacity, or a provider partnership. Those explanations may appear in online discussion, but they should not be presented as fact without an official source. The safest editorial wording is therefore: OpenAI announced the shutdown and removed the API; the single underlying cause has not been publicly established.

The practical consequence is clearer than the cause: applications that hard-code sora-2 or sora-2-pro need a new model ID, a new capability test, and a new price assumption. Do not silently swap a different model under the Sora name.

Which Sora alternative should you use?

Seedance 2.5: the higher-tier general replacement

Choose seedance-2.5 when you want a released, general-purpose text-to-video or image-to-video option and can accept a higher reference price. It has three active APIMaster routes in the October 5 snapshot.

Seedance 2.0 and Fast: balanced or throughput-focused

seedance-2.0 is the safer standard migration target. seedance-2.0-fast is better when cost and throughput matter more than matching the exact Sora look. Both use the asynchronous video workflow documented by APIMaster.

Seedance 2.0 Mini: lowest starting price

seedance-2.0-mini has the lowest observed starting price in this comparison. It is a good first candidate for short clips, batch experiments, and budget-sensitive pipelines, but validate quality and motion consistency on your own prompts.

Kling V3: motion and control workflows

Use kling-v3-omni for a broad video workflow, or kling-v3-motion-control when the key requirement is motion guidance rather than a Sora-compatible API name. The interfaces and output characteristics are not identical, so keep provider-specific fields isolated.

MiniMax H3 and Grok Imagine Video 1.5

minimax-h3 is a practical option when you need a different quality/price point with 768p and 2K variants. grok-imagine-video-1.5 is another active route for teams that want to evaluate a distinct provider. These are alternatives, not drop-in claims of identical output quality.

How do you migrate from Sora API?

Treat migration as a model change, not a string replacement:

1. Put the model ID in configuration and switch it to a tested replacement.
2. Keep prompts, reference images, duration, resolution, and aspect-ratio settings in a compatibility layer.
3. Re-run a small evaluation set for prompt adherence, temporal consistency, motion, safety behavior, and latency.
4. Update cost controls because replacements use different resolution multipliers and billing units.
5. Keep task polling and download handling separate from model-specific request fields.

The common APIMaster video pattern is to create an asynchronous task, poll the task ID, and download the completed asset. Start with a short clip:

{
  "model": "seedance-2.0",
  "prompt": "A cinematic tracking shot of a red train crossing a snowy bridge at sunrise",
  "duration": 5,
  "resolution": "720p"
}

Send the request to https://apimaster.ai/v1/videos/generations, poll https://apimaster.ai/v1/videos/task_<id>, and download the result from https://apimaster.ai/v1/videos/task_<id>/content. Confirm current fields in the video API documentation and the live model card.

Are users searching for a Sora replacement?

Yes, the search intent is visible in both English and Chinese query clusters: sora 2 api, sora 2 pro api, sora api unavailable, sora alternative, sora replacement, “Sora 替代”, and “Sora 视频 API”. APIMaster’s internal competitor baseline also found that the broader sora api term represented about 98% of the competitor’s English SEO search value in the December 2025–June 2026 window. That is a historical benchmark, not a claim about today’s search volume, but it is strong evidence that users look for both access and replacement options.

FAQ

Is Sora 2 still available through an API?

Not as a public APIMaster route as of October 5, 2026. OpenAI’s published API shutdown date was September 24, 2026, and APIMaster’s live marketplace check returned zero active routes.

Is Sora 2 Pro still available on OpenRouter?

The checked OpenRouter metadata had no usable endpoint and its tracker labeled Sora 2 Pro as removed on October 5, 2026. A directory page or historical model record should not be treated as a live route.

What is the best Sora alternative?

Start with seedance-2.0 for a balanced migration, seedance-2.0-mini for the lowest starting price, seedance-2.5 for a higher-tier general workflow, and Kling or MiniMax when their specific controls fit your workload better.

Can I keep the old Sora API request unchanged?

No. Keep the task lifecycle if it matches, but re-test model-specific fields, resolution, duration, safety behavior, output URLs, and billing. Do not assume a replacement produces identical results.

Are the Sora prices in the table current?

No. The Sora figures are historical reference prices only because both Sora IDs had zero active APIMaster routes on October 5, 2026. The replacement figures are live lowest-route observations from that date; the marketplace card wins when prices change.

How do I call a replacement model?

Create an APIMaster account, create a key in the API console, use https://apimaster.ai/v1, and set model to a currently listed ID such as seedance-2.0 or kling-v3-omni. Test one short generation before moving production traffic.

Sources and next steps

• OpenAI: What to know about the Sora discontinuation, checked October 5, 2026 for the consumer and API shutdown dates.
• OpenAI API deprecations, checked October 5, 2026 for the March 24 notification and September 24 API and model shutdown date.
• OpenAI Sora 2 announcement, checked October 5, 2026 for the product background.
• OpenAI Sora 2 model documentation, checked October 5, 2026 for the model record and API context.
• APIMaster marketplace data, checked October 5, 2026; only status=1 routes are counted, and the model card is authoritative.
• APIMaster Sora marketplace removal commit a13de05bc and documentation removal commit 7a5ae1cb3, both checked in the APIMaster repository.

Migrate with a released model: create an APIMaster account, create a key in the API console, call https://apimaster.ai/v1, and start with seedance-2.0, seedance-2.0-mini, seedance-2.5, or kling-v3-omni. Keep the model ID configurable so a future provider change does not require a full rewrite.