Databricks REST API
Google Gemini 2.5 Flash and Pro model retirement
Deprecated, no dateSubscribe to Databricks REST APIShare
Databricks REST API deprecated the model Google Gemini 2.5 Flash and Pro without giving a shutdown date yet.
In Databricks REST API's words
Google Gemini 2.5 Flash and Pro are scheduled for retirement
Facts
- API
- Databricks REST API
*.cloud.databricks.com - Model
Google Gemini 2.5 Flash and Pro- Kind
- Model retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Databricks REST API's own pages
Questions
When does Google Gemini 2.5 Flash and Pro shut down?
Databricks REST API deprecated the model Google Gemini 2.5 Flash and Pro without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Databricks REST API has not given a shutdown date yet.
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 Databricks REST API 10
-
No date
Anthropic Claude Sonnet 4Model retirement Deprecated, no date -
No date
DeepSeek V4 Flash (0731)Model retirement Deprecated, no date -
No date
DeepSeek V4 Pro (0813)Model retirement Deprecated, no date -
No date
DeepSeek V4.1 FlashModel retirement Deprecated, no date -
No date
GET /api/2.0/preview/sql/data_sourcesEndpoint removal Deprecated, no date -
No date
Google Gemini 2.5 FlashModel retirement Deprecated, no date -
No date
Google Gemini 2.5 ProModel retirement Deprecated, no date -
No date
Google Gemini 3 ProModel retirement Deprecated, no date -
No date
Llama 2 70B ChatModel retirement Deprecated, no date -
No date
Meta Llama 2, 3 and Code LlamaModel retirement Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.