OpenAI Shuts Down the Assistants API: What Breaks Today

OpenAI's Assistants API stopped working today, August 26, 2026 — a hard cutoff with no grace period, announced a full year ago and now enforced exactly on schedule. Every call to /v1/assistants, /v1/threads, and /v1/threads/runs now returns an error. If your product, internal tool, or client's chatbot was built on it, it's broken as of this morning unless someone already migrated it.

This isn't an obscure backend detail. The Assistants API has been the plumbing behind a huge share of "AI chatbot" builds shipped since late 2023 — support bots, internal knowledge assistants, multi-session agents wired into Zapier and no-code tools. A lot of small teams built on it once and never touched it again. Today is the day that stops being an option.

Quick Take

• What happened: OpenAI's Assistants API — /v1/assistants, /v1/threads, /v1/threads/runs — shut down completely on August 26, 2026, with no degraded mode and no extension.
• Why today specifically: OpenAI announced the deprecation on August 26, 2025, giving developers exactly one year's notice, per OpenAI's own deprecation documentation.
• The catch: There's no automated migration tool. Threads have to be exported and rebuilt as Conversations by hand, item by item.
• What survives: Vector stores and uploaded files carry over automatically into the Responses API's file search tool — it's specifically Thread and Assistant objects that need manual work.
• Who else is affected: Zapier is retiring its own ChatGPT (Assistants API) Zap steps on the same date, pushing users toward Responses API-based replacements.

What Actually Shut Down

The Assistants API launched at OpenAI's DevDay in November 2023 as the company's first real answer to "how do I build a stateful AI agent without managing conversation history myself." It handled threads, tool calls, and file retrieval in one package, and thousands of products — from internal support bots to full SaaS features — were built directly on top of it.

OpenAI released the Responses API in March 2025 as the intended long-term replacement, and confirmed the Assistants API's retirement a year ago. From today, the mapping is final: Assistants become prompts, Threads become Conversations, Runs become Responses, and Run Steps become Items. None of that happens automatically for existing integrations — it's a rebuild, not an upgrade.

Why the Missing Migration Tool Is the Real Story

The detail every developer thread on this keeps repeating is the same one: OpenAI never shipped an automated way to move Threads into Conversations. Teams have to iterate through each Thread's message history themselves and reconstruct it as a new Conversation object, then re-point their app at the new endpoints and re-test everything that depended on Run behavior.

For a hobby project, that's an afternoon. For a company running a production support bot with years of Thread history, it's a real engineering project — regression testing, observability, and rollback plans included — and it's one OpenAI gave exactly 365 days of notice to complete. Some of that history is now presumably just gone for teams that didn't act.

The one piece of good news: vector stores and any files you uploaded for retrieval aren't part of the breakage. OpenAI carried those over automatically into the Responses API's built-in file search tool, so document-grounded answers don't need to be re-indexed from scratch.

It's Not Just OpenAI's Own Customers

The ripple effect is bigger than people who called the API directly. Zapier is retiring its own ChatGPT (OpenAI) Zap steps that were built on the Assistants API on this exact date, moving customers toward new steps built on the Responses API instead. If you're one of the many small businesses running a Zapier automation that quietly used an "OpenAI Assistant" action somewhere in a workflow, that step needed rebuilding — whether or not you ever thought of yourself as someone who "uses the OpenAI API."

That's the pattern worth noticing: an API deprecation two layers down the stack turns into a support ticket for a no-code platform, then into a broken automation for someone who has never opened OpenAI's developer docs.

The Bigger Pattern at OpenAI

This is the second time this quarter OpenAI has pulled the plug on something with real usage behind it — it retired ChatGPT Atlas, its standalone AI browser, just over two weeks ago. Atlas was a consumer product killed for being a "side quest"; the Assistants API is developer infrastructure killed because a newer API does the same job better. Different reasons, same instinct: OpenAI is willing to break things that already have users if it simplifies what it has to maintain going forward.

That's a reasonable trade-off for OpenAI's own roadmap. It's a harder one if you're the developer who built a business on the assumption that a GA'd API — even a "beta" one, as Assistants technically remained — would stay stable. Compare that to how OpenAI is separately expanding into enterprise agent deployments with Presence: the company is clearly betting its future on agents, just not on the specific plumbing it shipped for them in 2023.

What To Do If You're Still On It

If your Assistants API calls are erroring out right now, you're not migrating anymore — you're doing incident response:

1. Confirm the break. Check whether your /v1/assistants or /v1/threads calls are actually failing versus a separate outage.
2. Export what you can. Pull Thread message history via whatever access you still have before deciding it's unrecoverable.
3. Stand up the Responses API path. Map Assistants → prompts and Threads → Conversations using OpenAI's migration guide, and budget real testing time — this is a rebuild of your conversation layer, not a config change.
4. Check every no-code tool touching OpenAI. Zapier, Make, and similar platforms may have quietly changed or removed steps tied to the old API; audit workflows rather than assuming they still fire.

Frequently Asked Questions

Is the Assistants API completely gone, or just for new users? Completely gone for everyone. As of August 26, 2026, calls to /v1/assistants, /v1/threads, and /v1/threads/runs return errors regardless of account age or usage history.

Do I lose my data permanently? Thread and Assistant objects are not automatically migrated and have no OpenAI-provided export tool, so unexported conversation history is effectively lost. Vector stores and uploaded files, however, carried over automatically to the Responses API's file search tool.

What should I migrate to? OpenAI's recommended path is the Responses API, released in March 2025, using its Conversations object for multi-turn state — the same one OpenAI says it built specifically to unify Chat Completions and Assistants API functionality.

Does this affect ChatGPT the consumer app, or just the API? Just the API. This is a developer-facing infrastructure change, separate from ChatGPT's own model lineup and features.

Is my Zapier automation affected even though I never used the OpenAI API directly? Possibly. Zapier is retiring its Assistants API-based ChatGPT steps on the same date, so any Zap using an older "OpenAI Assistant" action needs to be rebuilt on the newer step type.

Bottom Line

The Assistants API's shutdown is a reminder that "beta" labels and vague roadmap promises are not the same as a support commitment — OpenAI gave a full year of notice and still shipped no way to automatically carry your data forward. If you're affected, the fix isn't complicated, just unglamorous: export what you can, rebuild on the Responses API, and check every automation platform you've plugged into OpenAI along the way. For more on how OpenAI is reshaping its product lineup this year, see our coverage of the ChatGPT Atlas shutdown, or browse our latest Developer Tools coverage.