The Sora 2 API Deprecation Watch: Routing Checks Before September 24, 2026 is urgent because OpenAI lists the Videos API, sora-2, sora-2-pro, and related Sora 2 snapshots for shutdown on September 24, 2026. If a creator workflow, media pipeline, or internal campaign tool still depends on Sora 2 API jobs, treat the next two days as a freeze-and-verify window, not a normal model-selection cycle.
The practical answer: do not launch new production dependency on the Sora 2 API this week. Keep existing jobs behind a kill switch, export the usage and task history you need, verify every model ID and endpoint still in code, and prepare a fallback route through your video-generation gateway before the shutdown date.
Flatkey is useful in this review because it gives teams one video routing surface for supported video models, one usage-log workflow, and the same POST /v1/videos pattern for current Flatkey video routes. This article does not claim Flatkey currently routes Sora 2. The correct check is to list your account's current Flatkey models with GET /v1/models, then route new video tests only to models that are actually returned for your account.
Quick answer: should you build on the Sora 2 API now?
No. As of September 22, 2026, OpenAI's deprecations page says the Videos API and Sora 2 model aliases/snapshots were announced as deprecated on March 24, 2026 and are scheduled for removal from the API on September 24, 2026. The same deprecation table does not list a recommended replacement for the Videos API, sora-2, or sora-2-pro.
Use the Sora 2 API only for final extraction, auditing, or shutdown tests that you can afford to lose after the deadline. For any new creator workflow, put a video gateway check in front of model choice:
| Decision | Recommended action before September 24 |
|---|---|
| Existing Sora 2 production path | Freeze changes, verify remaining traffic, and add a hard fallback or shutdown path. |
| New campaign or product feature | Do not make Sora 2 the default route. Evaluate active video models instead. |
| Archived prompts and references | Export prompts, input references, task IDs, outputs, and usage records now. |
| Budget estimates | Treat Sora 2 pricing as historical or short-term only, not evergreen planning data. |
| Gateway configuration | Verify account-level model availability with GET /v1/models, not a cached blog post. |
Why this Sora 2 API topic needs a deprecation watch
Video-generation integrations fail differently from text integrations. A text model swap might break tone, JSON shape, or tool behavior. A video model swap can break the whole production lane: async task creation, queue latency, prompt format, image-reference handling, clip length, resolution, output URL lifetime, moderation rules, and cost per accepted clip.
That is why the Sora 2 API Deprecation Watch: Routing Checks Before September 24, 2026 should be treated as an operations checklist. The question is not just "which model is best?" The safer question is:
- Which routes still exist after September 24?
- Which request shape does each route need?
- Which outputs can your product accept without rework?
- Which logs prove the route, cost, and status of each job?
- Which fallback rule prevents a campaign calendar or user workflow from depending on a removed endpoint?
Official timeline to put in your review
Use the exact dates below in your migration ticket so the decision is auditable.
| Date | Source-backed fact | Team implication |
|---|---|---|
| March 24, 2026 | OpenAI says it notified developers using the Videos API and Sora 2 aliases/snapshots of deprecation. | Audit who received provider notices and whether they reached the owning team. |
| September 22, 2026 | OpenAI docs still describe Sora 2 and Sora 2 Pro as Videos API models, while the deprecation page lists their shutdown date. | Do not confuse available documentation with a durable route. |
| September 24, 2026 | OpenAI lists this as the shutdown date for the Videos API, sora-2, sora-2-pro, sora-2-2025-10-06, sora-2-2025-12-08, and sora-2-pro-2025-10-06. | Freeze new dependency and finish fallback checks before this date. |
OpenAI's deprecation glossary also matters: it defines deprecation as the process of retiring a model or endpoint, and says deprecated models and endpoints have a shutdown date when they will no longer be accessible. That makes the September 24 date a routing risk, not just a documentation note. Keep OpenAI's Sora video-generation guide, sora-2 model page, sora-2-pro model page, and pricing page open while you reconcile existing usage.
What to check in code before September 24
Start with a string search across your repos, workflow configs, notebooks, and task queues:
rg -n "sora-2|sora-2-pro|sora-2-2025|/v1/videos|openai\\.videos|Videos API|video_id"Then classify every hit:
| Finding | Risk | Action |
|---|---|---|
Hardcoded sora-2 or sora-2-pro | Calls can fail after shutdown. | Move model ID to config and remove it from default production policy. |
Direct https://api.openai.com/v1/videos call | Endpoint dependency may disappear. | Put it behind a route adapter or disable it before deadline. |
| Polling loop tied to OpenAI video IDs | Queue state and download behavior may no longer apply. | Add model-specific task-state adapters. |
| Cost calculator using Sora 2 per-second prices | Budget estimate becomes stale. | Mark as historical and replace with active route pricing. |
| Saved prompt templates labeled Sora 2 | Prompts may not transfer cleanly. | Re-test prompts against active video models with human review. |
The fastest useful review is not a giant rewrite. It is a route inventory with owners, traffic, fallback, and a decision for each call path.
Sora 2 API pricing is a short-term planning input
OpenAI's current model pages list Sora 2 and Sora 2 Pro video-generation prices by seconds and resolution. Sora 2 is listed at 720p only, while Sora 2 Pro is listed for 720p, 1024p, and 1080p. The pricing page also shows lower Batch API video rates.
That data is still useful for historical cost review. It is not enough for a September launch plan. If a model and endpoint are scheduled for shutdown on September 24, the cost question shifts from "is this price attractive?" to "what happens to queued, retrying, or scheduled jobs when the route disappears?"
Use this normalized field list instead:
video_route_review:
route_name: sora_2_legacy_shutdown_review
checked_at: 2026-09-22
owner: media_platform
endpoint: /v1/videos
model_ids:
- sora-2
- sora-2-pro
provider_shutdown_date: 2026-09-24
active_traffic_last_24h: fill_from_logs
queued_jobs: fill_from_queue
stored_outputs_exported: yes_or_no
fallback_route: model_id_or_feature_off
rollback_owner: team_or_person
user_visible_feature_flag: flag_nameFlatkey routing notes: what is verified and what is not
Flatkey's public docs describe a shared video-generation workflow:
POST https://router.flatkey.ai/v1/videoscreates an async video task.GET /v1/videos/{task_id}polls task status.GET /v1/videos/{task_id}/contentdownloads the completed video.GET /v1/modelsis the account-specific way to discover currently available models.
Flatkey's video-generation guide currently shows active video examples such as seedance-2.5, MiniMax-H3, grok-imagine-video, grok-imagine-video-1.5, veo-3.1-generate-preview, and veo-3.1-fast-generate-preview. The public model directory also shows video rows such as seedance-2.0-pro, veo-3.1-generate-preview, and Grok Imagine video models.
Do not infer Sora 2 availability from this article. The publish-safe statement is narrower: Flatkey supports a video-routing workflow and account-specific model discovery. If you are migrating away from a Sora 2 API dependency, verify the available Flatkey video routes in your own account before changing production traffic.
curl --fail-with-body -sS https://router.flatkey.ai/v1/models \
-H "Authorization: Bearer $FLATKEY_API_KEY" \
| jq '.data[] | select(.type == "video") | {id, owned_by, type}'If sora-2 is not returned, do not configure it. If a fallback model is returned, run a prompt-quality and output-shape test before routing real users.
Video fallback matrix for creator teams
Use this matrix to compare active routes after the Sora 2 API shutdown window.
| Route class | What to verify | Pass condition |
|---|---|---|
| Seedance route | content request shape, reference image roles, duration, resolution, audio option, usage record. | Task creates, polls, downloads, and records cost for the intended creator workflow. |
| Veo route | prompt request shape, supported resolution, duration, model status, per-second cost. | Same prompt class renders with acceptable latency and review quality. |
| MiniMax H3 route | content request shape, required resolution casing, reference media, output URL behavior. | Adapter handles its specific parameter rules without hidden defaults. |
| Grok Imagine video route | prompt request shape, output size, duration, repeatability limits. | Product accepts the output format and logs model-specific constraints. |
| Direct provider path | Provider account, auth, endpoint, limits, invoice owner, retention setting. | Direct fallback works even if gateway policy changes. |
The goal is not to find a one-line replacement for Sora 2. The goal is to isolate each model's request shape behind a video job adapter so your product code does not depend on one provider's retired endpoint.
For adjacent route reviews, keep the Veo API access checklist, Seedance vs Veo API routing review, AI model catalog guide, multimodal agent routing playbook, and Flatkey API quickstart close. Those pages cover the model-catalog, fallback, pricing, and first-call checks this Sora 2 API shutdown review points toward.
Sora 2 API Deprecation Watch: Routing Checks Before September 24, 2026 checklist
Run this checklist before the shutdown date.
- Search every repo, queue, notebook, and scheduler for
sora-2,sora-2-pro, Sora 2 snapshots, and/v1/videos. - Export remaining Sora 2 task IDs, prompts, input references, accepted outputs, failed outputs, timestamps, owners, and spend.
- Stop creating new long-lived campaign templates that assume Sora 2 availability.
- Add a product flag that disables Sora 2 routes without redeploying the whole app.
- Add a queue drain plan for jobs still pending near the deadline.
- Verify whether retries can accidentally recreate jobs against the retired endpoint.
- Choose candidate active video routes with
GET /v1/models, not memory or screenshots. - Re-test prompts with active models and record quality differences, output dimensions, duration, moderation failures, and cost.
- Update user-facing copy if any feature name implies "Sora" rather than a generic video generation route.
- Keep proof in usage logs: request ID, model ID, endpoint, status, cost, fallback reason, and output URL.
Copyable route review record
Use one record per video workload.
workload: product_trailer_generator
audience: creator_team
checked_at: 2026-09-22
legacy_route:
provider: openai
endpoint: /v1/videos
model: sora-2-pro
shutdown_date: 2026-09-24
current_status:
active_traffic: fill_from_logs
queued_jobs: fill_from_queue
stored_outputs_exported: yes_or_no
candidate_routes:
- model: fill_from_get_v1_models
request_shape: prompt_or_content
max_duration: model_limit
supported_resolution: model_limit
cost_unit: per_second
acceptance_checks:
- task_create_returns_id
- polling_reaches_terminal_state
- completed_video_downloads
- usage_log_records_model_status_cost
- fallback_reason_is_visible
decision:
owner: team_or_person
rollout: disabled_until_route_verified
rollback: direct_provider_or_feature_offFAQ
Is the Sora 2 API deprecated?
Yes. OpenAI's deprecation page lists the Videos API, sora-2, sora-2-pro, and related Sora 2 snapshots as deprecated with a September 24, 2026 shutdown date.
Can I still use Sora 2 API pricing for budget estimates?
Use it only for historical review or final short-term reconciliation. Because the route is scheduled for shutdown, creator teams should estimate new work from active video models and current account-level routes.
What replaces the Sora 2 API?
OpenAI's deprecation table does not list a recommended replacement for the Videos API or Sora 2 models. That means teams should run a route-level evaluation instead of assuming an official one-to-one substitute.
Does Flatkey support the Sora 2 API?
Do not assume that from this article. Flatkey supports an async video routing workflow and documents account-specific model discovery through GET /v1/models. Verify your account's current video model list before configuring any route.
What should a video gateway log?
At minimum: request ID, user or workspace, model ID, endpoint, task ID, status, retry count, fallback reason, duration, resolution, cost unit, final output URL, and whether the output was accepted or discarded.
Bottom line
The Sora 2 API Deprecation Watch: Routing Checks Before September 24, 2026 is a route-risk review, not a routine model comparison. If Sora 2 appears anywhere in production, freeze it, export what you need, and move future work to verified active video routes.
Flatkey can help with the next phase: one account-level model catalog, one async video endpoint pattern for supported video routes, and usage logs that make model, status, and cost visible. Start with GET /v1/models, compare current route costs on the pricing page, prove the route on a small prompt set, and only then move creator traffic.
