gemini-2.0-flash-live-001 model retirement

Stopped workingDecember 9, 2025Subscribe to Gemini APIShare

Calls to the model gemini-2.0-flash-live-001 stopped working on December 9, 2025.

The error you get

What Gemini API answers a call to gemini-2.0-flash-live-001 once the model is gone, as recorded from real responses:

Once it is closed to new API keys: HTTP 404

{"error":{"code":404,"message":"This model models/gemini-2.0-flash-live-001 is no longer available to new users. Please update your code to use a newer model for the latest features and improvements.","status":"NOT_FOUND"}}

Once it is shut down: HTTP 404

{"error":{"code":404,"message":"models/gemini-2.0-flash-live-001 is not found for API version v1beta, or is not supported for generateContent. Call ModelService.ListModels to see the list of available models and their supported methods.","status":"NOT_FOUND"}}

What to use instead of gemini-2.0-flash-live-001

Move to gemini-3.8-live, recommended by Google.

In Gemini API's words

Model: gemini-2.0-flash-live-001; Release date: April 9, 2025; Shutdown date: December 9, 2025; Recommended replacement: gemini-3.8-live

Gemini API, Deprecations page

Facts

API: Gemini API generativelanguage.googleapis.com
Model: gemini-2.0-flash-live-001
Kind: Model retirement
Takes effect: December 9, 2025
Calls after that day: Fail
Source: Deprecations page
Last updated: November 4, 2026
Verified: November 6, 2026, against Gemini API's own pages

Questions

When does gemini-2.0-flash-live-001 shut down?

Calls to the model gemini-2.0-flash-live-001 stopped working on December 9, 2025.

What happens to calls after December 9, 2025?

They have failed since December 9, 2025.

What error does gemini-2.0-flash-live-001 return once it is shut down?

Gemini API answers HTTP 404: "This model models/gemini-2.0-flash-live-001 is no longer available to new users. Please update your code to use a newer model for the latest features and improvements.". Send another model to fix it.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub