Unity Catalog Iceberg API Deprecation

Ashok_Vengala
New Contributor

‎02-18-2026 09:57 AM

 

Hello Databricks Team,

We are currently working with the Unity Catalog Iceberg API and have observed different behavior between older and newly created workspaces.

 

Observed error (new workspace):

{ "error": { "message": "Legacy Iceberg endpoints under /api/2.1/unity-catalog/iceberg/v1/ are deprecated. Please migrate to the new Iceberg REST API at /api/2.1/unity-catalog/iceberg-rest/v1/", "type": "BadRequestException", "code": 400 } }

 

In our older workspaces, the legacy Iceberg endpoint continues to work: /api/2.1/unity-catalog/iceberg/v1/ 

 

However, in a newly deployed workspace, calls to this endpoint return a deprecation error instructing us to use: /api/2.1/unity-catalog/iceberg-rest/v1/

At the same time, the older workspaces still support both the legacy and new endpoints.

 

Our questions

  1. From which Databricks workspace version, platform release, or rollout date was the legacy Iceberg endpoint (/unity-catalog/iceberg/v1/) disabled for new workspaces?

  2. Is this behavior tied to:

    • workspace creation date, or

    • a feature flag / control-plane rollout?

       

       

      According to the documentation below:

      👉https://docs.databricks.com/aws/en/external-access/iceberg

      It states that external Iceberg access is supported on Databricks Runtime 16.4 LTS and above.

      Could you please clarify:

      1. Does the deprecation or availability of the legacy Iceberg endpoint depend on the Databricks Runtime version (for example DBR 16.4 LTS or higher)?

      2. Where can we see which Databricks Runtime version is associated with a workspace deployment, particularly for API access (not cluster runtime)?

        

      Thank you for your guidance.
0 Kudos