OpenAI v1/prompts shuts down Nov 30, 2026: saved media recipes

OpenAI's deprecations page says the v1/prompts API and reusable prompt objects are scheduled to shut down on Nov 30, 2026. If the prompt you stored there drives media production, a Sume Format is the closest saved-recipe concept: you store the recipe once and call it by name. It is not a drop-in replacement for OpenAI prompt objects, and nothing here is a migration tool.

OpenAI facts are from its deprecations page; Format facts are from the Format API and Format contents docs, read 2026-10-01.

What exactly is OpenAI shutting down?

On June 3, 2026 OpenAI notified developers using reusable prompts in the dashboard and API that reusable prompt objects are being deprecated. The page lists two dates, and its migration advice is to move reusable prompt content into your application code.

What does a Sume Format store?

The Format API docs define a Format as a saved production recipe: a house style, an output contract, a playbook for one kind of video. Your backend calls it by name, with POST /v1/formats/{handle}/{slug}/runs, and gets finished media on media.sume.com back. A Format is a recipe for a whole production run in a fresh sandbox, so it covers more than a text template would.

Which part of my old prompt goes where?

The docs split every call into a recipe and a call. Use that split when you move a stored prompt: the stable parts become the recipe, and the parts that change per request become the call.

If you would rather keep the text in your own repository, as OpenAI suggests, that is also a valid choice. A Format only makes sense when the recipe is media production.

How do I change a saved recipe without clobbering a teammate?

The contents API lets you edit a Format's files over HTTP. To guard the whole package, send the package sha in an If-Match header; if the package has moved on, the write is refused with 409 format_package_sha_mismatch. Steps are in edit Sume Format files with If-Match.