---
title: "Save SQL-warehouse Auto Tune notification config"
method: PATCH
path: "/api/v1/databricks/warehouses/{warehouse_id}/auto-tune/config"
tags: ["DATABRICKS", "Databricks", "Databricks Warehouses"]
---

# Save SQL-warehouse Auto Tune notification config

`PATCH /api/v1/databricks/warehouses/{warehouse_id}/auto-tune/config`

Persist Auto Tune notification preferences for the warehouse. A
plain config write — never touches the enable/disable toggle or the
warehouse's own backoff-threshold storage.

## Path parameters

- `warehouse_id` string, required

## Query parameters

- `instance_id` integer, required — Tenant instance ID (workspace) the warehouse runs in
- `workspace_id` string, required — Required Databricks workspace_id — see the toggle/status endpoints.

## Headers

- `x-tenant` string, required

## Request body

- WarehouseAutoTuneConfigRequest — Request body for ``PATCH /databricks/warehouses/{id}/auto-tune/config``. Notification preferences ONLY — SQL-warehouse backoff keeps its own shipped storage/endpoints (``WarehouseAutoTuneBackoffConfiguration`` via the ``/auto-tune/toggle`` request). ``extra="forbid"`` rejects a ``backoff_policy`` key with a 422 instead of silently ignoring it, so a caller can never mistake this route for a way to touch warehouse backoff thresholds.
  - `notification_config` ClusterAutoTuneNotificationConfig — Cluster-wide Auto Tune notification preferences. Stored under the ``notification_config`` key in ``databricks_auto_tune_configuration.configuration``. References Slack channel ids from the tenant's ``notifications`` table by reference only — never a webhook URL inline (see ``NotificationConfigPublic`` for the same redaction rule on the generic notifications settings page).
    - `notify_backoffs_and_failures` boolean
    - `notify_changes_applied` boolean
    - `slack_enabled` boolean
    - `slack_channel_ids` integer[]
    - `email_enabled` boolean
    - `email_recipients` string[]

## Response `200`

Successful Response

- WarehouseAutoTuneConfigResponse — Response for the SQL-warehouse Auto Tune config read/write endpoints. No ``backoff_policy`` field — deliberately narrower than ``ClusterAutoTuneConfigResponse`` (see the request schema's docstring).
  - `notification_config` ClusterAutoTuneNotificationConfig — Cluster-wide Auto Tune notification preferences. Stored under the ``notification_config`` key in ``databricks_auto_tune_configuration.configuration``. References Slack channel ids from the tenant's ``notifications`` table by reference only — never a webhook URL inline (see ``NotificationConfigPublic`` for the same redaction rule on the generic notifications settings page).
    - `notify_backoffs_and_failures` boolean
    - `notify_changes_applied` boolean
    - `slack_enabled` boolean
    - `slack_channel_ids` integer[]
    - `email_enabled` boolean
    - `email_recipients` string[]
  - `entity_type` string

## Other responses

- `403` — Not authorized
- `422` — Validation Error

## Changes

- **2026-09-02** `fcb62c79da95` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/myaltimate/apis/fastapi/changes/api/v1/databricks/warehouses/:warehouse_id/auto-tune/config/patch.md)

---

[API](https://skmtc.dev/myaltimate/apis/fastapi.md) · [All operations](https://skmtc.dev/myaltimate/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/myaltimate/fastapi/revisions/fcb62c79da95/schema)