---
title: "Per-day Possible Savings for an all-purpose cluster"
method: GET
path: "/api/v1/databricks/clusters/{cluster_id}/auto-tune/savings-trends"
tags: ["DATABRICKS", "Databricks", "Databricks Clusters"]
---

# Per-day Possible Savings for an all-purpose cluster

`GET /api/v1/databricks/clusters/{cluster_id}/auto-tune/savings-trends`

## Request

- Base URL: `https://api.myaltimate.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.myaltimate.com/api/v1/databricks/clusters/{cluster_id}/auto-tune/savings-trends`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer

Per-day Spend × savings-pct Possible Savings series. ``actual`` is
always empty — cluster Auto Tune has no realized-savings mart.

## Path parameters

- `cluster_id` string, required

## Query parameters

- `instance_id` integer, required: Tenant instance ID (workspace)
- `workspace_id` string, nullable: Optional Databricks workspace_id to scope the lookup.
- `start_date` string, date, required: Start date
- `end_date` string, date: End date
- `granularity` string: Time granularity: 'day', 'week', or 'month'
- `navigationSource` string, nullable

## Headers

- `x-tenant` string, required

## Response `200`

Successful Response

- AutoTuneSavingsTrendsResponse: Per-day auto-tune savings for a job, split into realized and potential. ``actual`` holds savings on runs where an applied recommendation was in effect; ``potential`` holds the savings those runs would have earned from the active recommendation had it been applied. Each series is bucketed by the run window (``period_start_time``).
  - `actual` AutoTuneSavingsTrendPoint[], required
    - `period` string, required
    - `dbu_savings` number
    - `infra_savings` number
    - `rec_type` string, nullable
  - `potential` AutoTuneSavingsTrendPoint[], required
    - `period` string, required
    - `dbu_savings` number
    - `infra_savings` number
    - `rec_type` string, nullable
  - `granularity` string, required

## Other responses

- `403`: Not authorized
- `404`: No ClickHouse database configured
- `422`: Validation Error

## Changes

- **2026-09-02** `fcb62c79da95`: 2 info
  - added the optional property `actual/items/rec_type` to the response with the `200` status
  - added the optional property `potential/items/rec_type` to the response with the `200` status

[Operation history](https://skmtc.dev/myaltimate/apis/fastapi/changes/api/v1/databricks/clusters/:cluster_id/auto-tune/savings-trends/get.md)

---

[API](https://skmtc.dev/myaltimate/apis/fastapi.md) - [All operations](https://skmtc.dev/myaltimate/apis/fastapi/llms.txt) - [OpenAPI document](https://skmtc.dev/myaltimate/apis/fastapi/revisions/e0c123b49501?raw)