/v1/fine-tunes — Retired

Quick fix — copy & paste

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

# OpenAI: /v1/fine-tunes (deprecated)
model = "/v1/fine-tunes"

# Replacement
model = "/v1/fine_tuning/jobs"

// OpenAI: /v1/fine-tunes (deprecated)
const model = "/v1/fine-tunes";

// Replacement
const model = "/v1/fine_tuning/jobs";

"model": "/v1/fine-tunes"

"model": "/v1/fine_tuning/jobs"

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: /v1/fine-tunes
• The model `/v1/fine-tunes` has been deprecated
• The model `/v1/fine-tunes` does not exist or you do not have access to it

Replacement options

• /v1/fine_tuning/jobs Compare token cost →

Other OpenAI deprecations

• dall-e-2 2026-05-12 · 4d
• dall-e-3 2026-05-12 · 4d
• computer-use-preview 2026-07-23 · 76d
• gpt-4o-audio-preview-2024-12-17 2026-07-23 · 76d
• gpt-4o-mini-audio-preview-2024-12-17 2026-07-23 · 76d

What this means for your code

/v1/fine-tunes is a fine-tuned model based on a deprecated base model. Fine-tuned models cannot be migrated by changing a string. The base model's deprecation means your fine-tune will stop working. You need to re-fine-tune on a supported base.

/v1/fine-tunes was retired by OpenAI on 2024-01-04. API calls now return an error and the model is no longer accessible. New code should use /v1/fine_tuning/jobs; legacy code that still references this model id needs to be updated immediately.

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:

grep -rn '"/v1/fine-tunes"' --include="*.py" .

grep -rn '"/v1/fine-tunes"' --include="*.{js,ts,tsx,jsx}" .

grep -rn "/v1/fine-tunes" .

Migration checklist

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

1. 1. Identify the deprecated base model used by your fine-tune
2. 2. Re-prepare your training data — format may need updating for the new base
3. 3. Run a fresh fine-tuning job against a current base model
4. 4. Validate the new fine-tune meets your evals before swapping in
5. 5. Plan a parallel-run period where both the old and new fine-tunes serve traffic