OpenAI Kills the Assistants API on August 26. Here's What Actually Breaks
Most people have never typed the words "Assistants API" and never will. That's the point: it's plumbing, not a product, sitting behind a support bot on a shopping site, a custom tool at work, an automation someone built once and forgot about. None of that needs you to do anything on August 26. You'll just notice the moment it breaks.
Aug 26, 2026
when the Assistants API stops responding entirely
per OpenAI's deprecations page, described as a hard cutoff, not a slowdown.
1 year
notice OpenAI gave before pulling the plug
the sunset was announced August 26, 2025, per OpenAI's developer community post, exactly a year ahead.
Dec 18, 2024
when OpenAI already retired the first version of this same API
the original v1 beta of the Assistants API was shut off in favor of v2, per OpenAI's own migration thread. This is the second forced rebuild in under two years.
0
automated tools OpenAI provides to convert old chat threads
per OpenAI's migration guide, Threads have to be manually rebuilt as Conversations.
What the Assistants API actually did
It let developers bolt a persistent AI assistant onto their product without building their own chat-history system, plus access to OpenAI-hosted tools like Code Interpreter and File Search, per OpenAI's own FAQ. It's launched two eras of apps this way: first the v1 beta, retired December 18, 2024 in favor of v2, and now v2 itself, going away entirely on August 26.
If you use Zapier
Zapier has already pulled the deprecated ChatGPT actions from its editor for new Zaps. Existing Zaps built on "Conversation With Assistant (Legacy)" get auto-migrated to a new Conversation action powered by the Responses API, but Zapier leaves the migrated Zap switched off until you review and re-enable it yourself, per Zapier's own notice. Zaps built on Create Assistant, Upload File, or Find Assistant have no automatic replacement at all.
| If you use... | What happens on August 26 |
|---|---|
| A Zap built on 'Conversation With Assistant (Legacy)' | Auto-migrated to the new Conversation action, but left turned off until you go review and re-enable it. |
| A Zap built on Create Assistant, Upload File, or Find Assistant | No automatic replacement. It breaks and has to be rebuilt with current actions. |
| A custom chatbot or support widget built directly on the API | Every request errors out the moment the date turns, per OpenAI's own docs. |
| Azure OpenAI's Assistants feature | Follows the same retirement, per Microsoft's own guidance for Azure customers. |
Why OpenAI is doing this
OpenAI's stated case is that the Responses API is the more capable successor, built to support newer features like deep research, MCP connections, and computer use that the older Assistants architecture wasn't designed for, per OpenAI's migration guide. Retiring the older API forces every integration onto one modern foundation instead of OpenAI maintaining two systems side by side indefinitely.
What to actually do if you're not the one building it
- 1If an AI feature you use is inside a bigger product (a shopping site's support chat, a work tool, a browser extension), there's nothing for you to migrate. It's on that app's developers to move to the Responses API before August 26.
- 2If you built a Zap yourself using a ChatGPT (OpenAI) action, open the Zap editor now and check whether it's one of the deprecated actions listed above, before it breaks mid-workflow.
- 3If something you rely on suddenly starts erroring out on or after August 26 with no warning, this deprecation is the most likely reason, worth checking before you assume it's your own setup.
What exactly happens to the Assistants API on August 26, 2026?
Every request to /v1/assistants, /v1/threads, and /v1/runs starts returning an error, with no grace period and no degraded mode, per OpenAI's own deprecations page.
What replaces the Assistants API?
The Responses API for generating replies, plus a new Conversations API for storing chat history. OpenAI says these together now cover what the Assistants API used to do.
Will my old chat history be moved over automatically?
No. OpenAI's migration guide has no bulk conversion tool. Old Threads have to be manually rebuilt as Conversations by whoever built the app.
I use Zapier. Do I need to do anything?
Check your Zaps. Zapier auto-migrates 'Conversation With Assistant (Legacy)' Zaps to a new action, but leaves them switched off until you review and re-enable them. Zaps using Create Assistant, Upload File, or Find Assistant have no automatic replacement and need to be rebuilt.
Is this the first time OpenAI has shut down this API?
No. The original v1 beta of the Assistants API was already retired on December 18, 2024 in favor of v2. August 26, 2026 is the second full rebuild developers on this API have had to do.
Try the tools ✦
Free browser tools that never upload your files.