Skip to content

Build2 publishers2 min readPublished

OpenAI routes its shutdown notices to the account that created the API key

OpenAI's own deprecations page lists four cutoffs between 24 September and 23 October 2026. Finding out whether they touch your code takes one look at the Usage dashboard, in an account plenty of buyers cannot sign into.

The Engineer · Build desk

Illustration accompanying OpenAI routes its shutdown notices to the account that created the API key

What happened

  • OpenAI shut the Assistants API on 26 August 2026, and the next cutoffs are 24 September for the Videos API and sora-2, 28 September for the last legacy completion snapshots, and 23 October for gpt-3.5-turbo and gpt-4.
  • The dates come from OpenAI's official deprecations page, which the dev.to author says he checked on 16 August 2026 and reconfirmed on 13 September.
  • Runtimewire reports that Disney, which had agreed in December 2025 to license over 200 characters for Sora and to invest $1 billion in OpenAI, said it would not proceed once OpenAI decided to close the product.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • cost Migration labour was never in the fixed-price build quotes of 2023 and 2024, which compared implementation cost and monthly token spend, so the buyer absorbs each retirement cycle out of pocket.
  • constraint A new model string does not satisfy the 24 September date, because the Videos API closes with no listed successor and OpenAI is out of the business of supplying video models to developers.
  • exposure A company whose key lives in someone else's account never receives the email, so it meets the deprecation as an outage in a live business process.
  • precedent With the six-month floor tied to generally available status, anything preview or specialist in a stack now needs a fallback written at build time, not a calendar reminder.

The check takes one login. Sign in to platform.openai.com with the account that pays the API bill, open Usage, and switch the breakdown to group by model; the names in the last 30 days are what your code actually calls [13]. On Anthropic, open the Usage page in the Claude Console and click Export, which returns a CSV broken down by API key and by model, a procedure Anthropic documents for auditing deprecated models [14].

Failure on the day is abrupt. According to the dev.to write-up, a call to a retired model returns an error and the integration stops [9]. OpenAI's documentation says "software relying on OpenAI models may need occasional updates to keep working" [11], and the same write-up notes that Anthropic writes almost the same sentence [12].

Not every cutoff is the same job. On 28 September the old completion snapshots, gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106, are folded into gpt-5.6-terra, so the work is a model string and a regression pass [3]. On 24 September the Videos API goes along with sora-2 and sora-2-pro, and the deprecation page lists no replacement [2]. Runtimewire reports that the same date ends OpenAI's run as a supplier of generative video models to developers, five months after the consumer app and website closed on 26 April [19][20][25]. sora-2 shipped on 30 September 2025 [21], which gave the API 359 days of life [3].

Four of the published cutoffs fall inside the 29 days between 24 September and 23 October [1]. Twenty days of notice, which is what gpt-5.4-cyber got, works out at about a ninth of the six-month minimum, and that minimum applies to generally available models [8][2]. Six months is a generous notice period for an API, and it is worth nothing in an inbox nobody reads.

The softest number here is the one the routing argument rests on. The dev.to author says the retirement notice goes by email to the developer account that created the API key, and that half the time that account belongs to an agency no longer working with the client [10]. Half is an estimate from one practice's client base, and the piece does not say how it was counted. For it to describe your setup, your key inventory has to look like his, and the Usage view settles that in a few minutes [13]. Where nobody at the company can sign in at all, which the write-up calls the most common case [15], the remedy on the record is administrative: the provider account opened in the company's name, paid by the company, with the outside developer added as an invited user [17].

What to watch

  • Whether OpenAI names any replacement path for video generation before the Videos API closes on 24 September.
  • Whether the 23 October date for gpt-3.5-turbo and gpt-4 holds; the deprecations page has already been reconfirmed once since 16 August.
  • Whether more models ship with sub-month notice like gpt-5.4-cyber's twenty days, which would leave non-GA models outside any usable planning window.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories