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

> Discover supported profile fields and create a LinkedIn monitor.

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/`). |
| `fields` | Yes | Nonempty selection of keys from field discovery. Fixed after creation. |
| `frequency` | No | Default `1w`. Range: 7–365 days. Units: `d`, `w`, `m` (30 days). |

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

```json theme={null}
{
  "linkedin_url": "https://www.linkedin.com/in/example",
  "fields": ["headline", "current_company_name", "skills"],
  "frequency": "1w"
}
```

Returns `201` with the standard monitor response: `monitor_type: "linkedin"`, one row, and the selected fields in `struct`.

## CSV upload

Use [POST /monitors/upload](https://docs.sixtyfour.ai/api-reference/monitors/monitors-endpoints.md#create-monitor-from-a-file) with `monitor_type: "linkedin"`. The CSV must contain exactly one column of LinkedIn person URLs with a nonempty header (for example, `linkedin_url`). The first line is always treated as the header.

## Check behavior

The first successful check establishes a baseline. Later checks report exact field differences. Checks read stored data; they do not scrape LinkedIn or run an LLM.

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

[Monitor APIs](https://docs.sixtyfour.ai/api-reference/monitors/monitors-endpoints.md) and [webhooks](https://docs.sixtyfour.ai/api-reference/monitors/monitor-notifications.md) work as usual.

## Pricing

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

## Errors

See [Handling Errors](https://docs.sixtyfour.ai/api-reference/errors.md#linkedin-monitor-validation-and-access).


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