Okapi Okapi
Add to GitHub

Databricks REST API Zhipu AI GLM 5.2 model retirement

Deprecated, no date

Databricks REST API deprecated the model Zhipu AI GLM 5.2 without giving a shutdown date yet.

In Databricks REST API's words

Zhipu AI GLM 5.2 is now a legacy model

Databricks REST API, Changelog

Facts

API
Databricks REST API *.cloud.databricks.com
Model
Zhipu AI GLM 5.2
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 Zhipu AI GLM 5.2 shut down?

Databricks REST API deprecated the model Zhipu AI GLM 5.2 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 8

  1. No date Anthropic Claude Sonnet 4Model retirement Deprecated, no date
  2. No date GET /api/2.0/preview/sql/data_sourcesEndpoint removal Deprecated, no date
  3. No date Google Gemini 2.5 FlashModel retirement Deprecated, no date
  4. No date Google Gemini 2.5 ProModel retirement Deprecated, no date
  5. No date Google Gemini 3 ProModel retirement Deprecated, no date
  6. No date /api/2.0/preview/sql/alerts*Version retirement Deprecated, no date
  7. No date /api/2.0/preview/sql/queries*Version retirement Deprecated, no date
  8. No date /api/2.0/preview/sql/permissions/*Endpoint removal 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.

Add to GitHub