---
title: "Update Freshness Schedule"
method: PATCH
path: "/api/v1/sdk/freshness/schedules/{schedule_id}"
tags: ["public-api", "public-freshness"]
---

# Update Freshness Schedule

`PATCH /api/v1/sdk/freshness/schedules/{schedule_id}`

## Request

- Base URL: `http://localhost:8000`
- URL: `http://localhost:8000/api/v1/sdk/freshness/schedules/{schedule_id}`
- Auth: none declared

Update a freshness schedule.

**SDK Usage:**
```python
client = Client()
client.freshness.update_schedule(
    schedule_id="123",
    is_active=False,
)
```

## Path parameters

- `schedule_id` string, required

## Headers

- `Authorization` string

## Request body

- UpdateFreshnessScheduleRequest: Request to update a freshness schedule via SDK. Note: Validation for explicit mode requirements is handled by the service layer, which has access to existing schedule state. This allows PATCH semantics where users can switch to explicit mode while relying on existing expected_interval_hours.
  - `check_interval` string, nullable
  - `expected_interval_hours` number, nullable
  - `freshness_column` string, nullable
  - `monitoring_mode` string, nullable
  - `is_active` boolean, nullable

## Response `200`

Successful Response

- StandardResponse: Standard API response wrapper.
  - `success` boolean, required
  - `data` unknown
  - `message` string, nullable
  - `error` string, nullable
  - `meta` object, nullable

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/anomalyarmor/apis/anomalyarmor-api.md) · [All operations](https://skmtc.dev/anomalyarmor/apis/anomalyarmor-api/llms.txt) · [OpenAPI document](https://skmtc.dev/anomalyarmor/apis/anomalyarmor-api/revisions/51c755fb5d0b?raw)