LinkedIn monitors are enabled per organization. Contact support to turn them on.
List supported fields
List every profile field a LinkedIn monitor can watch.cURL
next_cursor is always null.
Create a LinkedIn monitor
SendPOST /v1/monitors with type: "linkedin" and one row per profile.
name, first_check, is_active, webhook_url, webhook_event_types, metadata, and the Idempotency-Key header work as they do in Create monitor. tier is ignored and research_plan is not accepted, because LinkedIn checks run no research.
The response is 201 with the monitor. fields maps each selected key to its label. A field with a condition is returned as an object holding its label in description and the condition in criteria.
Create from a file
Use Create monitor from a file withtype: "linkedin" in settings. These rules differ from research uploads:
settingsneedssubject_type: "person"andkey_columns: ["linkedin_url"], and takes noresearch_plan.frequencydefaults to1w, with the range above. Optionalcriteriaapplies to every profile in the file.- 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.
Update a LinkedIn monitor
Update monitor applies, with these rules:frequencymust stay within 7 to 365 days.mmeans 30 days here too, and is stored in days.tieris not accepted.- The selected fields cannot change. Create a new monitor to change them.
criteriareplaces 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 return422.
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. 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. Thepayload.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. Theirprevious_value and current_value hold text values as they are and other values as compact JSON. The payload differs from a research monitor’s: