Create Contact Radar
Create a contact radar for person-level tracking.
Authorizations
Body
The type of contact activity to track. Choose based on your tracking needs:
• contact_job_changes: Track when someone leaves, gets promoted, or changes roles at a company. Requires domain and at least one identifier (email, profile_url, or full_name).
• contact_social_engagements: Track when people engage (react, comment, repost) with a specific person's social media posts. Requires profile_url.
• contact_social_posts: Track social media posts FROM a specific person. Monitors when the contact themselves posts content on social platforms. Requires profile_url.
contact_job_changes, contact_social_engagements, contact_social_posts URL where we'll send radar findings. Optional — if omitted, the radar is poll-only and updates are available via GET /v1/updates.
"https://webhook.site/your-webhook-id"
Optional RFC 3339 timestamp with a UTC offset defining the earliest eligible source event. TAMradar normalizes and stores the value in UTC. It must represent now or a past instant and may be at most five calendar years old. A five-second server tolerance exists only for clock skew; it is not future scheduling. When omitted, the radar creation timestamp is used as the effective cutoff.
Deprecated compatibility field. It is accepted and stored but has no effect. Use updates_since to request historical eligibility.
LinkedIn profile URL of the person to track.
• For contact_job_changes: Optional LinkedIn person profile using the /in/ path (used alongside other identifiers). Company, school, and legacy /pub/ URLs are rejected. • For contact_social_engagements: Required LinkedIn, X, or Twitter profile (this is whose engagement activity we'll track) • For contact_social_posts: Required LinkedIn, X, or Twitter profile (this is whose posts we'll track)
Protocol (https://) is automatically added if missing.
"https://www.linkedin.com/in/johndoe"
Company domain where the contact works.
• Required for contact_job_changes (the company you're tracking them at) • Optional for contact_social_engagements (not needed for social tracking) • Optional for contact_social_posts (can be used to associate the contact with a company)
Automatically normalized - strips protocol, www, paths.
"stripe.com"
Contact's individual email address. Used for contact_job_changes only. Role-based, shared, and placeholder addresses such as info@, sales@, and noreply@ are rejected. At least one identifier (email, profile_url, or full_name) is required for job change tracking.
"john.doe@stripe.com"
Contact's full name. Used for contact_job_changes only. At least one identifier (email, profile_url, or full_name) is required for job change tracking. full_name is not used as a duplicate key; duplicate matching uses email or the normalized LinkedIn profile URL within the same domain and radar type.
"John Doe"
Optional metadata to attach to this radar. Values must be strings only. Use for internal tracking like account_id, customer_id, or deal_stage. Returned with every webhook.