> ## 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.

# LinkedIn Monitors (Legacy)

> Discover supported profile fields and create a LinkedIn monitor.

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

Watch selected fields in Sixtyfour's stored LinkedIn profiles. Requires LinkedIn monitoring access for your organization.

## List supported fields

```http theme={null}
GET /monitors/linkedin/fields
```

Returns `200` with all supported fields, without pagination. Response excerpt:

```json theme={null}
[
  { "key": "full_name", "label": "Full name" },
  { "key": "headline", "label": "Headline" }
]
```

## Create a LinkedIn monitor

```http theme={null}
POST /monitors/linkedin
```

| Field | Required | Description |
| - | - | - |
| `linkedin_url` | Yes | LinkedIn person URL (`/in/`). Stored as `https://www.linkedin.com/in/{name}`, without a query string or fragment. |
| `fields` | Yes | Nonempty selection of keys from field discovery. Fixed after creation. |
| `criteria` | No | Map of selected field keys to optional alert conditions, up to 10,000 characters per condition. Omitted or blank conditions add no restriction. Editable through the update endpoint. Unknown or unselected keys return `422`. |
| `frequency` | No | Default `1w`. Range: 7 to 365 days. Units: `d`, `w`, `m`. On a LinkedIn monitor `m` means 30 days, not minutes as on a research monitor. A frequency in `m` is stored in days, so `1m` is returned as `30d`. |

Other options (`name`, `first_check`, `is_active`, webhook settings, `metadata`, and `idempotency_key`) follow [standard monitor creation](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#create-monitor). Here, `name` defaults to `LinkedIn monitor`; `tier` and `research_plan` are not accepted.

```bash cURL theme={null}
curl -X POST "https://api.sixtyfour.ai/monitors/linkedin" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "linkedin_url": "https://www.linkedin.com/in/example",
    "fields": ["headline", "current_company_name", "skills"],
    "criteria": {"headline": "Only a promotion to a leadership role"},
    "frequency": "1w"
  }'
```

```python Python theme={null}
import requests

response = requests.post(
    "https://api.sixtyfour.ai/monitors/linkedin",
    headers={"x-api-key": "YOUR_API_KEY"},
    json={
        "linkedin_url": "https://www.linkedin.com/in/example",
        "fields": ["headline", "current_company_name", "skills"],
        "criteria": {"headline": "Only a promotion to a leadership role"},
        "frequency": "1w",
    },
)
response.raise_for_status()
monitor = response.json()
print(monitor["id"], monitor["status"], monitor["next_run_times"])
```

```javascript JavaScript theme={null}
const response = await fetch("https://api.sixtyfour.ai/monitors/linkedin", {
  method: "POST",
  headers: { "x-api-key": "YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    linkedin_url: "https://www.linkedin.com/in/example",
    fields: ["headline", "current_company_name", "skills"],
    criteria: { headline: "Only a promotion to a leadership role" },
    frequency: "1w",
  }),
});
if (!response.ok) {
  throw new Error(`Failed to create monitor: ${await response.text()}`);
}
const monitor = await response.json();
console.log(monitor.id, monitor.status, monitor.next_run_times);
```

Returns `201` with the standard monitor response: `monitor_type: "linkedin"`, one row, and the selected fields in `struct`. `tier` reads `low` but has no effect, because LinkedIn checks run no research.

```json theme={null}
{
  "monitor_type": "linkedin",
  "id": "4c2a9e7b-1f3d-4b8a-9c6e-2d7f5a1b3e90",
  "org_id": "acme",
  "team_id": "5e1d9c3a-7b2f-4e6a-8c1d-3f9a2b4c6d8e",
  "name": "LinkedIn monitor",
  "frequency": "1w",
  "struct": {
    "current_company_name": "Current company",
    "headline": {"description": "Headline", "criteria": "Only a promotion to a leadership role"},
    "skills": "Skills"
  },
  "tier": "low",
  "subject_type": "lead",
  "research_plan": null,
  "is_active": true,
  "disabled_reason": null,
  "webhook_url": null,
  "webhook_event_types": ["monitor.field.changed"],
  "metadata": null,
  "last_run_at": null,
  "next_run_times": [
    "2026-10-01T00:00:00+00:00",
    "2026-10-08T00:00:00+00:00",
    "2026-10-15T00:00:00+00:00"
  ],
  "row_count": 1,
  "active_row_count": 1,
  "status": "active",
  "created_at": "2026-09-28T17:05:12.482Z",
  "updated_at": "2026-09-28T17:05:12.482Z"
}
```

## CSV upload

Use [POST /monitors/upload](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#create-monitor-from-a-file) with `monitor_type: "linkedin"` in `config`. These rules differ from research uploads:

* `config` needs `key_columns: ["linkedin_url"]` and `subject_type: "lead"`, and takes no `research_plan`. `struct` keys must be field keys from discovery; their values are replaced with the field labels. Optional `criteria` maps selected `struct` keys to alert conditions and applies to every profile in the upload; conditions are returned in the corresponding `struct` objects. `frequency` defaults to `1w`, with the range above. `tier` is ignored.
* The CSV must contain exactly one column of LinkedIn person URLs with a nonempty header, under any name (for example, `linkedin_url`). The first line is always treated as the header. Empty lines are skipped, and every other line must hold a valid person URL.
* Duplicate profiles are rejected after URL normalization.

To use a file uploaded earlier with `POST /storage/csv/upload`, send its `handle_id` to [Create monitor](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#rows-from-an-upload-handle) with the same settings. The response is `201` with `status: "starting"`, and rows are added in the background.

## Update a LinkedIn monitor

[Update monitor](https://docs.sixtyfour.ai/api-reference/legacy/monitors-endpoints.md#update-monitor) applies, with these rules:

* `frequency` must stay within 7 to 365 days. `m` means 30 days here too, and is stored in days.
* `tier` is not accepted.
* The selected fields cannot change. Create a new monitor to change them.
* `criteria` replaces the complete criteria map. Omit it to keep existing criteria; send `{}` to clear them. Keys must be selected fields. Unknown or unselected keys, `null`, and non-string values return `422`.

```bash cURL theme={null}
curl -X POST "https://api.sixtyfour.ai/monitors/MONITOR_ID/update" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "criteria": {
      "job_title": "Only if this role started within the last month"
    }
  }'
```

```python Python theme={null}
import requests

response = requests.post(
    "https://api.sixtyfour.ai/monitors/MONITOR_ID/update",
    headers={"x-api-key": "YOUR_API_KEY"},
    json={
        "criteria": {
            "job_title": "Only if this role started within the last month"
        }
    },
)
response.raise_for_status()
monitor = response.json()
print(monitor["struct"])
```

```javascript JavaScript theme={null}
const response = await fetch("https://api.sixtyfour.ai/monitors/MONITOR_ID/update", {
  method: "POST",
  headers: { "x-api-key": "YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    criteria: {
      job_title: "Only if this role started within the last month",
    },
  }),
});
if (!response.ok) {
  throw new Error(`Failed to update monitor: ${await response.text()}`);
}
const monitor = await response.json();
console.log(monitor.struct);
```

Updating criteria preserves the monitor ID, rows, history, baseline, and schedule. All member rows receive the new criteria atomically, including paused rows. Future checks use the new criteria; a check that already loaded the old settings keeps them. Replaying a completed check preserves its original decision. Changing criteria alone does not reassess unchanged values or publish an event.

## Check behavior

The first successful check establishes a baseline. Later checks compare field values and assess candidate differences for significance. Equivalent wording, unordered-list reordering, and uncertain changes are suppressed; see [Values](https://docs.sixtyfour.ai/api-reference/legacy/monitors-overview.md#values). Checks read Sixtyfour's stored profile data and run no research.

A check reads the latest copy of the profile that Sixtyfour holds, so a change on LinkedIn is reported only after that copy is updated. The `payload.search_updated_at` of each `change` and `established` event says when the copy it read was last updated.

Each candidate field is assessed using its before/after values, the full current stored profile, the check date, and its own criteria. A change is reported and charged only when it is significant and its criteria are confidently satisfied. Criteria cannot create an event for a field whose value did not change, and one field's criteria do not restrict another field.

For example, `"criteria": {"job_title": "Only if this role started within the last month"}` uses the matching position's start date. Missing dates or an ambiguous position suppress the change. Month-only dates do not establish an exact day: a month overlapping the cutoff cannot confidently satisfy a rolling date window.

Successful assessments advance the baseline even when a change is suppressed. The same unchanged value is not reassessed on the next check. If the full profile cannot be read or the assessment fails, the check fails without publishing or charging and keeps the previous baseline for retry.

A missing or deleted profile records a failed check, preserves the baseline, and is retried on future scheduled checks.

A check that finds changes your balance cannot cover sends `monitor.execution.failed`, records no `change` or `error` event, and keeps the previous values. Its `completion` event, listed with `include_completions=true`, still records the values read. A later check reports the changes once your balance covers them.

## Event payloads

LinkedIn monitors write the [standard event types](https://docs.sixtyfour.ai/api-reference/legacy/monitors-overview.md#events). Their `previous_value` and `current_value` hold text values as they are and other values as compact JSON. The `payload` differs from a research monitor's:

| `event_type` | `payload` |
| - | - |
| `established`, `change` | `source` (`"linkedin"`), `sources` (the profile URL), `previous` and `current` (the raw values, such as a list rather than its JSON text), `search_updated_at` (when the copy read was updated), and the monitor's `metadata`. There is no `confidence` or `justification`. |
| `completion` | Written for every check that reads the profile, with or without changes. Holds `values` (every selected field as read), `checked_at`, `result` (a summary of the check), and `search_updated_at`. |
| `error` | `reason`: `linkedin_profile_not_found` or `linkedin_profile_deleted`. |

## Pricing

See [Credit Costs](https://docs.sixtyfour.ai/guides/credits-and-pricing.md#monitors).

## Related

* [Monitors Overview](https://docs.sixtyfour.ai/api-reference/legacy/monitors-overview.md)
* [Monitor Notifications](https://docs.sixtyfour.ai/api-reference/legacy/monitor-notifications.md)
* [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.