Migrating off Videos API — retirement date and replacement
OpenAI is retiring Videos API on 2026-09-24 — in 11 days. The provider has not named a replacement in its own documentation, so the migration target is your decision. This page is built from OpenAI’s official deprecation notice and is rechecked weekly; the source link is below.
When is Videos API being deprecated?
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| Videos API | OpenAI | 2026-09-24 | — not named |
Source: OpenAI deprecation notice · announced 2026-03-24
What should I migrate Videos API to?
OpenAI has not published a successor for this model. That makes the decision yours, and it is worth treating as an opportunity to compare providers rather than defaulting to whatever is nearest. Endpoint responsiveness is measurable; model quality claims mostly are not.
Measured latency of the OpenAI API host
| Region | p50 TTFB | p95 | Uptime | Probes |
|---|---|---|---|---|
| Asia (Tokyo) | 199 ms | 269 ms | 99.7% | 290 |
| Europe (Germany) | 204 ms | 397 ms | 100% | 288 |
| South America (São Paulo) | 241 ms | 461 ms | 100% | 288 |
| US (Central) | 124 ms | 190 ms | 100% | 289 |
Edge latency to the provider’s API host over the last 24 hours, measured from 4 regions. This measures the endpoint, not the model: swapping models on the same host does not change these figures, which is exactly why they are useful when deciding whether to stay with OpenAI or leave. Compare providers →
What else retires on 2026-09-24?
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| sora-2 | OpenAI | 2026-09-24 | — not named |
| sora-2-2025-10-06 | OpenAI | 2026-09-24 | — not named |
| sora-2-2025-12-08 | OpenAI | 2026-09-24 | — not named |
| sora-2-pro | OpenAI | 2026-09-24 | — not named |
| sora-2-pro-2025-10-06 | OpenAI | 2026-09-24 | — not named |
Same shutdown date. If you call more than one of these, they are one migration, not several.
Other OpenAI models being retired
| Model | Provider | Retires | Replacement |
|---|---|---|---|
| babbage-002 | OpenAI | 2026-09-28 | gpt-5.6-terra |
| davinci-002 | OpenAI | 2026-09-28 | gpt-5.6-terra |
| gpt-3.5-turbo-1106 | OpenAI | 2026-09-28 | gpt-5.6-terra |
| gpt-3.5-turbo-instruct | OpenAI | 2026-09-28 | gpt-5.6-terra |
| ft-babbage-002 | OpenAI | 2026-10-23 | gpt-5.6-terra |
| ft-davinci-002 | OpenAI | 2026-10-23 | gpt-5.6-terra |
| ft-gpt-3.5-turbo | OpenAI | 2026-10-23 | gpt-5.6-terra |
| ft-gpt-4 | OpenAI | 2026-10-23 | gpt-5.6-sol |
How is this calendar maintained?
Entries are pulled from provider documentation by an automated weekly job and every one carries a link to its source. Nothing is inferred from blog posts or social media. When a provider changes a date, the change appears here after the next run and is visible in the changelog. The full calendar across all providers is on the deprecations page, and this provider’s own list is at OpenAI deprecations.