This page documents the original routes, which keep working. For new integrations, use the
/v1 routes in LinkedIn Monitors. Legacy maps each original route to its /v1 replacement.List supported fields
200 with all supported fields, without pagination. Response excerpt:
Create a LinkedIn monitor
Other options (
name, first_check, is_active, webhook settings, metadata, and idempotency_key) follow standard monitor creation. Here, name defaults to LinkedIn monitor; tier and research_plan are not accepted.
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.
CSV upload
Use POST /monitors/upload withmonitor_type: "linkedin" in config. These rules differ from research uploads:
configneedskey_columns: ["linkedin_url"]andsubject_type: "lead", and takes noresearch_plan.structkeys must be field keys from discovery; their values are replaced with the field labels. Optionalcriteriamaps selectedstructkeys to alert conditions and applies to every profile in the upload; conditions are returned in the correspondingstructobjects.frequencydefaults to1w, with the range above.tieris 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.
POST /storage/csv/upload, send its handle_id to Create monitor with the same settings. The response is 201 with status: "starting", and rows are added in the background.
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: