Requests to the model gemini-3.5-flash are automatically redirected to the model gemini-3.6-flash
The model gemini-3.5-flash is marked as deprecated in Gemini API. All requests to it are automatically redirected to the model gemini-3.6-flash. The announcement recommends updating the model identifier.
The announcement in Gemini API Changelog dated 8 October 2026 marks the model gemini-3.5-flash as deprecated and states that it has been replaced by the model gemini-3.6-flash. All requests using the original identifier are automatically redirected to the replacement model.
The announcement recommends changing the identifier in the configuration to gemini-3.6-flash or gemini-3.8-flash and reviewing the Gemini 3.6 Flash guide. Automatic redirection therefore routes requests to the model gemini-3.6-flash; the model gemini-3.8-flash is listed as another option for a manual update.
Why it matters
For applications using the original identifier, the model actually used changes even without developer intervention. When assessing their outputs, it is therefore necessary to account for the fact that requests are now processed by the model gemini-3.6-flash.
Two audiences, two different impacts
What this means
For individuals
A developer using Gemini API has two recommended options when updating the configuration: the identifier gemini-3.6-flash or gemini-3.8-flash.
For a business
Model management in business applications must account for the automatic change: the original identifier in the deployed configuration no longer refers to the model that actually processes requests.
DevelopmentCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.