OpenAI DEPRECATED TRIVIAL 76 days left

gpt-4o-mini-realtime-preview-2024-12-17 — Deprecated

Deprecated
Shutdown
2026-07-23
Status
deprecated
Replacement
gpt-realtime-mini

Quick fix — copy & paste

Choose your language. The "before" block matches the deprecated call; the "after" block is the drop-in replacement.

Breaks on 2026-07-23
# OpenAI: gpt-4o-mini-realtime-preview-2024-12-17 (deprecated)
model = "gpt-4o-mini-realtime-preview-2024-12-17"
Use this instead
# Replacement
model = "gpt-realtime-mini"

This migration was generated automatically from the model rename. If your code does more than swap a model id, double-check request/response shapes against the official OpenAI migration guide.

Error messages

Seeing one of these? You're in the right place.

  • model_not_found: gpt-4o-mini-realtime-preview-2024-12-17
  • The model `gpt-4o-mini-realtime-preview-2024-12-17` has been deprecated
  • The model `gpt-4o-mini-realtime-preview-2024-12-17` does not exist or you do not have access to it

Replacement options

Other OpenAI deprecations

What this means for your code

gpt-4o-mini-realtime-preview-2024-12-17 is a realtime model used over a WebSocket or WebRTC for low-latency speech-to-speech. Realtime models maintain stateful sessions over a persistent connection. Migrating means updating session.update events, tool definitions, and any custom turn-detection logic. Pricing is per minute of input and output audio.

OpenAI has scheduled gpt-4o-mini-realtime-preview-2024-12-17 for shutdown on 2026-07-23. That gives you 76 days to migrate. Until then the model still works, but every API call after that date will return a model_not_found error.

Find every call in your codebase

Before you change anything, locate every place the deprecated model id is referenced. Search source files, environment files, feature flags, and config repos. Use these commands from your project root:

Python projects

grep -rn '"gpt-4o-mini-realtime-preview-2024-12-17"' --include="*.py" .

JavaScript / TypeScript projects

grep -rn '"gpt-4o-mini-realtime-preview-2024-12-17"' --include="*.{js,ts,tsx,jsx}" .

Anywhere (configs, scripts, infra)

grep -rn "gpt-4o-mini-realtime-preview-2024-12-17" .

Migration checklist

Steps in order. Skip any that don't apply, but read the whole list — for realtime models, the non-obvious steps are usually the ones that break in production.

  1. 1. Update the model id in your session.update event payload
  2. 2. Verify supported voices and modalities (audio, text) on the new model
  3. 3. Re-test turn detection (server VAD vs none) and interruption handling
  4. 4. Audit tool definitions — function calling schema may have changed
  5. 5. Reconnect logic should fall back to a still-supported model on session failure

Will this migration cost more?

Switching from gpt-4o-mini-realtime-preview-2024-12-17 to gpt-realtime-mini could change your costs significantly. Calculate the exact difference for your prompts.

Open the cost calculator →