Gemini Routes 3.7 Flash and 3.5 Flash to Newer Model Strings
The 8 October API note says gemini-3.7-flash requests go to gemini-3.8-flash, and gemini-3.5-flash requests go to gemini-3.6-flash.
Direct answer
The Gemini API release notes for 8 October 2026 say gemini-3.7-flash is deprecated and requests to it are routed to gemini-3.8-flash. gemini-3.5-flash is deprecated and requests to it are routed to gemini-3.6-flash.
The Gemini API release notes for 8 October 2026 open with two Flash deprecations. gemini-3.7-flash is deprecated and replaced by gemini-3.8-flash. All requests to gemini-3.7-flash are automatically routed to gemini-3.8-flash. The note tells callers to update the model string to gemini-3.8-flash. gemini-3.5-flash is deprecated and replaced by gemini-3.6-flash. All requests to gemini-3.5-flash are automatically routed to gemini-3.6-flash. The suggested strings are gemini-3.6-flash or gemini-3.8-flash.
The same date has a separate Deep Research deprecation with a shutdown day. These two Flash lines do not use that day. They describe automatic routing of the old model strings. The page does not print a price difference between the old and new strings.
A nearby image-model line is not this routing
Under 6 October the same page says Gemini Nano Banana 2.1, id gemini-nano-banana-2.1, is generally available, and that gemini-3.1-flash-image is deprecated with no shutdown date announced. That pair is an image model and its replacement. It is not the 3.7 Flash or 3.5 Flash text-model routing from 8 October.
Source: Gemini API release notes.
FAQ
- Does the note give a shutdown day for these two Flash ids?
- It says the requests are automatically routed. It does not print a separate shutdown date for gemini-3.7-flash or gemini-3.5-flash.
- What string does the note suggest for a 3.5 Flash caller?
- gemini-3.6-flash, or gemini-3.8-flash.