---
title: "What changed for your watched keys between two dates"
method: GET
path: "/v1/account/watch/diff"
tags: ["Account"]
---

# What changed for your watched keys between two dates

`GET /v1/account/watch/diff`

## Request

- Base URL: `https://api.greencalculus.com`
- URL: `https://api.greencalculus.com/v1/account/watch/diff`
- Auth: HTTP bearer

The reporting-period question, answered directly: per key, the value at each boundary, whether it moved, the versions that touched it, and a proof link per side — the evidence a restatement decision needs. A `from` older than the change record clamps to the archive watershed and the response says so.

## Query parameters

- `from` string, date, required
- `to` string, date

## Response `200`

Per-key boundary values and proof links

- WatchDiff: What changed for the watched keys between two dates — the value at each boundary, whether it moved, and a proof link per side. Dates resolve to data versions through the change record; a `from` older than the record clamps to the archive watershed and says so.
  - `from` string
  - `to` string
  - `note` string: Present when there is nothing to diff, or when a boundary was clamped.
  - `keys` object[]
    - `key` string
    - `from` object
      - `version` string
      - `value` number, nullable
      - `unit` string, nullable
      - `held` boolean
    - `to` object
      - `version` string
      - `value` number, nullable
      - `unit` string, nullable
      - `held` boolean
    - `changed` boolean
    - `versions_touching` string[]
    - `proof` object
      - `from` string
      - `to` string

## Other responses

- `400`: Missing or malformed from/to
- `401`: No valid key or session

---

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