Skip to content
NewsIncident

OpenAI Assistants API Shut Down August 26, Breaking Production Apps With No Grace Period

· by Pondero Newsdesk

The short version

The OpenAI Assistants API went offline on August 26, 2026. Every call to /v1/assistants, /v1/threads, and /v1/threads/runs now returns an error. Migration to the Responses API is required immediately with no grace period.

OpenAI Assistants API Shut Down August 26, Breaking Production Apps With No Grace Period

The OpenAI Assistants API went offline on August 26, 2026, exactly one year after its deprecation announcement. Every call to /v1/assistants, /v1/threads, and /v1/threads/runs now returns an error. There is no grace period, no extension, and no automated migration tool. Any production application built on these endpoints is breaking for end users today.

What happened

OpenAI launched the Responses API in March 2025 and announced the Assistants API would be retired, per the OpenAI developer community thread. The company said it had folded the core Assistants features into the Responses API before the cutoff, including code interpreter and persistent conversations. The August 26, 2026 shutdown arrived on schedule.

Developers must now route assistant logic through the Responses API and persistent chat history through the Conversations API, per OpenAI's deprecations page. OpenAI published a migration guide titled "Assistants to Conversations" at developers.openai.com/api/docs/assistants/migration, but provided no automated tool to convert existing Threads or assistant definitions. Thread history must be reconstructed manually.

One significant gap flagged in the community thread before shutdown: programmatic Prompt creation is not yet available in the Responses API. Developers who built workflows around dynamic Assistant creation via API call must now create Prompts through the OpenAI dashboard instead. That breaks any fully automated pipeline that previously called POST /v1/assistants at runtime. OpenAI has not committed a timeline for closing this gap.

Why it matters

Any application routing calls to /v1/assistants, /v1/threads, or /v1/threads/runs is returning errors for end users right now. There is no fallback and no informal extension. The concrete remediation steps:

  • Audit your codebase for calls to the deprecated endpoints.
  • Rebuild assistant definitions as Prompts in the Responses API. If your workflow previously created Assistants programmatically, dashboard-only creation is the current path.
  • Reconstruct thread history manually. OpenAI provided no data export utility for Threads.
  • Validate the Conversations API session-persistence model before deploying to production. It handles state differently than Threads did.

If migration is not yet complete, communicating the outage to affected users is the immediate priority. The deprecated endpoints will not return to service.

What to watch next

Track OpenAI's developer changelog at developers.openai.com/api/docs/deprecations for updates on programmatic Prompt creation in the Responses API. Expect SaaS vendors that embedded the Assistants API to publish incident disclosures within 48-72 hours as customer-facing AI features break and engineering teams trace the root cause.

Sources