gemini-1.0-pro model retirement
Stopped workingSubscribe to Gemini APIShare
Calls to the model gemini-1.0-pro stopped working on October 14, 2026.
The error you get
What Gemini API answers a call to gemini-1.0-pro once the model is gone, as recorded from real responses:
{"error":{"code":404,"message":"This model models/gemini-1.0-pro 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"}}
{"error":{"code":404,"message":"models/gemini-1.0-pro 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-1.0-pro
gemini-2.5-pro, named first, is closed to some callers (Google: "we are limiting access to the 2.5 models to users who have actively used them in the past." Projects that already called it keep it; new projects are told to use 3.5 Flash-Lite or 3.8 Flash.). No replacement that holds is named yet. Nothing about a 1.0-era integration survives unchanged: the SDK, the request shape and the safety-setting enums have all been replaced since.
Facts
- API
- Gemini API
generativelanguage.googleapis.com - Model
gemini-1.0-pro- Kind
- Model retirement
- Takes effect
- October 14, 2026
- Calls after that day
- Fail
- Source
- models.dev
- Last updated
- Verified
- , against Gemini API's own pages
Questions
When does gemini-1.0-pro shut down?
Calls to the model gemini-1.0-pro stopped working on October 14, 2026.
What happens to calls after October 14, 2026?
They have failed since October 14, 2026.
What error does gemini-1.0-pro return once it is shut down?
Gemini API answers HTTP 404: "This model models/gemini-1.0-pro 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.
More from Gemini API 10
-
gemini-1.0-flashModel retirement Stopped working -
gemini-omni-flash-previewModel retirement Stopped working -
veo-3.1-fast-generate-previewModel retirement Stopped working -
veo-3.1-generate-previewModel retirement Stopped working -
veo-3.1-lite-generate-previewModel retirement Stopped working -
gemini-2.5-flash-native-audio-preview-12-2025Model retirement Stops workingin 11 days -
gemini-2.5-flash-preview-ttsModel retirement Stops workingin 11 days -
gemini-2.5-pro-preview-ttsModel retirement Stops workingin 11 days -
gemini-3.1-flash-live-previewModel retirement Stops workingin 11 days -
gemini-3.1-flash-tts-previewModel retirement Stops workingin 11 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.