> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sixtyfour.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitors Overview (Legacy)

> Keep watched people and company fields current on a schedule, with sources and webhook notifications when they change.

> [!NOTE]
>
> This page documents the original routes, which keep working. For new integrations, use the `/v1` routes in [Monitors Overview](https://docs.sixtyfour.ai/api-reference/monitors/monitors-overview.md). [Legacy](https://docs.sixtyfour.ai/api-reference/legacy.md) maps each original route to its `/v1` replacement.

> [!NOTE]
>
> Monitors require access for your organization. Contact [support@sixtyfour.ai](mailto:support@sixtyfour.ai).

Create and manage monitors through the [Monitor Endpoints](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md), the workflow [`monitor` block](https://docs.sixtyfour.ai/api-reference/workflows/workflow-blocks#monitor), or the Monitors page in the Sixtyfour web app.

[LinkedIn monitors](https://docs.sixtyfour.ai/api-reference/legacy/linkedin-monitors.md) compare selected stored profile fields without research. They share the monitor APIs and notifications. The check flow, tiers, and frequency units below describe research monitors.

## Concepts

| Term | Meaning |
| - | - |
| Monitor | One table with one schedule. Its settings (watched fields, frequency, tier, webhook) apply to every row. |
| Row | One person or company in the table, with its own current values, event history, and on/off switch. |
| Subject | The values that identify a row, taken from its `key_columns` (for example `company_name` and `domain`). A subject never changes. |
| Watched fields | The fields the monitor keeps current, passed as `struct`. Same shape as the enrichment `struct`: a description string, or an object with `type`, `description`, and `subfields` for nested fields. |
| Baseline | The values a row currently holds for its watched fields. Every reported change updates it. |
| Subject type | `company` re-derives fields with Company Intelligence. `lead` uses People Intelligence. |
| Tier | Depth of the full re-check: `low`, `medium`, or `high`. |
| Snapshot | The whole table as it stood at a moment. A snapshot is recorded for each second in which any value is established or changes. |

A column cannot be both a key column and a watched field. Two rows with the same subject values are rejected; the workflow `monitor` block watches such rows once.

## How a check works

Every tick of the schedule checks each active row.

```mermaid theme={null}
flowchart TD
    A[Schedule tick] --> B[Each active row]
    B --> C{Baseline setup still needed?}
    C -- Yes --> D[Enrich watched fields at the monitor tier]
    D --> E[Report uploaded values that are already stale]
    C -- No --> F[Probe: has anything changed since the last check?]
    F -- No --> G[completion event]
    F -- Yes --> H[Re-check watched fields at the monitor tier]
    H --> I[change event per field that moved]
    E --> J[Webhook notification]
    G --> J
    I --> J
```

* Baseline setup: a watched field whose name matches a column in the input row starts from that cell. A row missing any watched value is enriched at the monitor's tier: missing fields get their first value, and every supplied value that is already out of date is reported as a `change`. Rows that supply every watched value skip setup and start with the probe on the schedule.
* Probe: later checks read the row's known sources and new search results to decide whether any watched field changed. A check with no likely change ends here with a `completion` event.
* Re-check: when the probe finds a likely change, the monitor re-derives the watched fields at its tier and records one `change` event per field whose value moved, with sources, confidence, and a justification. A value equal to the field's last reported value is not reported again.
* Failures: a check that cannot finish records an `error` event and leaves its time window open. The next check re-examines the same window, so no change is lost.

## Events

Every event from one check shares an `event_group_id`.

| `event_type` | Meaning |
| - | - |
| `change` | A watched field's value changed. Carries `previous_value`, `current_value`, and a `payload` with `sources`, `confidence` (0–100, or `null` when not scored), `justification`, and the monitor's `metadata`. A change found by a re-check also carries `hint`, what the probe saw change. `payload.first_run` is `true` when setup found a supplied value stale. |
| `established` | A field received its first value, either supplied at creation or found by a check. Not a change. |
| `completion` | The check ran and found no change. `payload` describes what was checked and the time window (`window_from`, `window_to`). Hidden from event listings unless `include_completions=true`. |
| `error` | The check could not run or finish. `payload.reason` says why: `insufficient balance`, or `probe did not run`, `re-check did not run`, or `baseline re-check did not run` when that step failed; the next check retries the same window. |

[LinkedIn monitors](https://docs.sixtyfour.ai/api-reference/legacy/linkedin-monitors.md#event-payloads) write the same event types with different payloads and their own error reasons.

## Values

Research monitors store every watched value as text. A list answer is stored as its items joined by `; `, and an object as `key=value` pairs joined by `; `.

A re-check reports a change only when the new value still differs from the baseline after these rules:

* Case, repeated whitespace, and trailing punctuation are ignored.
* Numbers compare by value: `1981.0` equals `1981`, and `1,200` equals `1200`.
* A list answer compares without regard to order.
* An empty answer, such as `unknown` or `not found`, keeps the previous value and reports nothing.
* A reworded value judged to state the same fact, such as a school's full name in place of its short name, is not reported.

Starting values from row cells are stored as text too. Send them as strings, with list items joined by `; `. A list or object cell is stored in a different text form, and the first re-check can report it as a change.

LinkedIn monitors compare stored profile values exactly. Text values are returned as they are; lists, numbers, and booleans are returned as compact JSON, such as `["Python","SQL"]` or `true`. Any difference is a change, including a list in a new order.

## How to read changes

| To read | Use | Notes |
| - | - | - |
| One row's check, as it finishes | A [row notification](https://docs.sixtyfour.ai/api-reference/legacy/monitor-notifications.md#row-notification-payload), then [List row events](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#list-row-events) with its `event_group_id` | `monitor.field.changed` covers checks with changes. Add `monitor.execution.completed` and `monitor.execution.failed` to hear about every check. |
| Every row one run changed | [`monitor.run.completed`](https://docs.sixtyfour.ai/api-reference/legacy/monitor-notifications#whole-monitor-completion) or [List monitor runs](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#list-monitor-runs), then [Get a run's changed rows](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#get-a-runs-changed-rows) | Only for runs whose `status` is `completed`. Poll the runs list as well: a `failed` run sends no notification. |
| When each cell last changed | [List latest changes](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#list-latest-changes) | Timestamps for the whole monitor in one request, without values. |
| One field's history on one row | [List row events](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#list-row-events) with `field` | At most the newest 500 events. |
| The whole table at one moment | [Download snapshot](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#download-snapshot) with an `as_of` from [List snapshots](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#list-snapshots), or `latest` | One CSV, one row per subject. |
| The whole table across a period | [Export history](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#export-history) | A ZIP with one CSV per snapshot. |

## Frequency

On a research monitor, `frequency` is a whole number followed by a unit: `m` (minutes), `h` (hours), `d` (days), or `w` (weeks), for example `90m`, `6h`, `1d`, or `2w`. The default is `1d`.

LinkedIn monitors read `m` as 30 days, not minutes, and have their own default and range. See [Create a LinkedIn monitor](https://docs.sixtyfour.ai/api-reference/legacy/linkedin-monitors.md#create-a-linkedin-monitor).

* The supported range is `1h` to `365d`, so `1m` (one minute) is rejected on a research monitor.
* Schedules align to UTC. An hourly monitor fires at the top of each hour, a daily monitor at 00:00 UTC, and a weekly monitor (`1w` or `7d`) on Thursdays at 00:00 UTC. Longer intervals do not follow the calendar: a `30d` monitor fires every 30 days, not on the same date each month. `next_run_times` on every monitor response lists the next three fire times.
* `first_check: "now"` (default) runs setup immediately for rows missing watched values. Rows that supply every watched value wait for the schedule. `first_check: "next_tick"` defers every row to the first scheduled fire.
* Checks never overlap. If a tick is still running when the next one is due, the next one is skipped.

## Billing

For setup, probe, and re-check charges, see the [Credit Costs](https://docs.sixtyfour.ai/guides/credits-and-pricing.md#monitors).

Creating a research monitor, or changing its `tier`, checks tier access and the team's spend limit but not your balance. Each check is paid for when it runs. A research check your balance cannot cover is skipped and records an `error` event. For LinkedIn monitors, see [Check behavior](https://docs.sixtyfour.ai/api-reference/legacy/linkedin-monitors.md#check-behavior).

## Access and ownership

* A monitor belongs to the team of the credential that created it. Only that team can see or change it.
* A monitor runs on behalf of the API key or user that created it. If that key is revoked or expires, the user leaves the organization or team, or the team is archived, its rows pause; see [Disabled reasons](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#disabled-reasons).
* When the team's spend limit is reached, checks are skipped until the limit clears.

For error responses, see [Handling Errors](https://docs.sixtyfour.ai/api-reference/legacy/errors.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.