Search people, add results to a List, and poll events safely.
This REST walkthrough searches people, creates or reuses a dedicated List, adds up to five matches, then collects that List’s events into a local checkpoint file. It does not send outreach or modify an ATS.
Do not reuse the final cursor for the next scheduled poll. Start a new pass with the last successful checkpoint minus a small overlap.
Treat person.linkedin_url as the ATS/CRM join key and event.id as the activity deduplication key.
Honor Retry-After on 429; retry bounded GETs on 429/5xx, but reconcile uncertain POST/PATCH requests before retrying.
Event visibility is evaluated at request time and there is no published retention SLA. Add periodic reconciliation if completeness matters.
For exact repeat searches, save and replay the echoed query on people search. Target discovery uses a different schema and is not an exact replay of the graph search. See Search query compatibility.