Skip to main content
POST
/
v1
/
radars
/
contacts
curl --request POST \ --url https://api.tamradar.com/v1/radars/contacts \ --header 'Content-Type: application/json' \ --header 'x-api-key: <api-key>' \ --data ' { "domain": "stripe.com", "radar_type": "contact_job_changes", "webhook_url": "https://webhook.site/your-webhook-id", "email": "john.doe@stripe.com", "profile_url": "https://example.social/profile/johndoe", "full_name": "John Doe", "custom_fields": { "account_id": "acc_123", "customer_id": "cust_456", "deal_stage": "negotiation" } } '
{ "status": "success", "code": 201, "timestamp": "2024-03-20T10:15:30.000Z", "message": "Radar created successfully", "data": { "radar_id": "12f96f87-4ce9-49fa-bf09-ca08b23015a6", "radar_type": "contact_job_changes", "domain": "stripe.com", "webhook_url": "https://webhook.site/your-webhook-id", "radar_status": "active", "created_at": "2024-03-20T10:15:30.000Z", "deactivated_at": null, "next_charge_at": "2024-04-20T10:15:30.000Z", "custom_fields": { "account_manager": "sarah.smith", "deal_value": "50000", "tags": "key-account, enterprise" }, "email": "john.doe@stripe.com", "profile_url": "https://example.social/profile/johndoe", "full_name": "John Doe" } }

Documentation Index

Fetch the complete documentation index at: https://docs.tamradar.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
x-api-key
string
header
required

Body

application/json
​
radar_type
enum<string>
required

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.

Available options:
contact_job_changes,
contact_social_engagements,
contact_social_posts
​
webhook_url
string<uri>

URL where we'll send radar findings. Optional — if omitted, the radar is poll-only and updates are available via GET /v1/updates.

Example:

"https://webhook.site/your-webhook-id"

​
profile_url
string<uri>

LinkedIn profile URL of the person to track.

• For contact_job_changes: Optional LinkedIn profile (used alongside other identifiers) • For contact_social_engagements: Required LinkedIn profile (this is whose engagement activity we'll track) • For contact_social_posts: Required LinkedIn profile (this is whose posts we'll track)

Protocol (https://) is automatically added if missing.

Example:

"https://www.linkedin.com/in/johndoe"

​
domain
string

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.

Example:

"stripe.com"

​
email
string<email>

Contact's email address. Used for contact_job_changes only. At least one identifier (email, profile_url, or full_name) required for job change tracking.

Example:

"john.doe@stripe.com"

​
full_name
string

Contact's full name. Used for contact_job_changes only. At least one identifier (email, profile_url, or full_name) required for job change tracking.

Example:

"John Doe"

​
custom_fields
object

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.

Example:
{
  "account_id": "acc_123",
  "customer_id": "cust_456",
  "deal_stage": "negotiation"
}

Response

Radar created successfully

​
status
enum<string>
Available options:
success
​
code
enum<integer>
Available options:
201
​
message
string
​
data
object
​
timestamp
string<date-time>