Skip to main content
POST
Create a company radar
Set updates_since to include recent activity. Choose a date a few weeks or months back for eligible activity from that period plus ongoing updates. If omitted, most radars start at their exact creation time, not the start of today: even a post published one minute earlier is excluded. Your first check may return no results, and updates may take time to arrive.New hires and promotions use UTC calendar-month precision: set updates_since to an earlier month to include activity from that month onward. If omitted, eligibility starts in the month the radar was created.To see sample findings first, use Preview where supported. Preview chooses its own lookback and does not accept updates_since.
Example dates are illustrative. Calculate updates_since from your chosen lookback.

Authorizations

x-api-key
string
header
required

Body

application/json
domain
string
required

The domain to track (e.g., stripe.com). Protocol, www, paths, and query parameters are automatically normalized.

Example:

"stripe.com"

radar_type
enum<string>
required

The type of company activity to track

Available options:
company_new_hires,
company_job_openings,
company_promotions,
company_reviews,
company_mentions,
company_social_posts,
company_social_posts_cxo,
company_social_engagements
webhook_url
string<uri>

Webhook URL to receive radar updates and notifications. Optional — if omitted, the radar is poll-only and updates are available via GET /v1/updates.

Example:

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

updates_since
string<date-time>

Optional RFC 3339 timestamp with a UTC offset. Recommended for recent activity: choose a date weeks or months back. If omitted, most radars start at their exact creation time, not the start of today; even a post published one minute earlier is excluded. Initial checks may return no results; immediate updates are not guaranteed. New hires and promotions compare UTC calendar months, starting with the cutoff month (creation month if omitted). Contact job changes monitor detected changes, not historical job moves. TAMradar stores the timestamp in UTC. It must be now or in the past, at most five calendar years old. The five-second clock-skew tolerance does not allow future scheduling.

include_historical
boolean
deprecated

Deprecated compatibility field. It is accepted and stored but has no effect. Use updates_since to request historical eligibility.

departments
string[]

Optional array of department names to filter results. See API documentation for valid department values.

Example:
seniorities
string[]

Optional array of seniority levels to filter results. See API documentation for valid seniority values.

Example:
job_titles
string

Boolean expression filtering company radar results by job title. When provided, job_titles takes precedence over departments and seniorities; those fields do not affect matching. Operators AND, OR, and NOT must be uppercase. A single word may be unquoted; multi-word phrases must use double quotes. Matching is case-insensitive for title terms. A quoted phrase means contiguous phrase containment within the candidate title, not exact whole-title equality: "Marketing Manager" matches "Senior Marketing Manager" but not "Marketing Operations Manager". EXACT("Marketing Manager") requires the complete normalized title to equal "Marketing Manager"; it does not match "Senior Marketing Manager" and does not expand aliases or abbreviations. EXACT must be uppercase and requires exactly one double-quoted title. Operator precedence is NOT, then AND, then OR; parentheses control grouping. Each term must contain at least two searchable characters and may contain at most 100 characters. The complete expression may contain at most 9,000 characters and 32 nested Boolean groups. A malformed expression returns HTTP 400 with an actionable job_titles error.

Example:

"EXACT(\"Sales Operations Manager\") OR (\"sales operations\" AND (manager OR VP))"

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 campaign_id. Returned with every webhook.

Example:
profile_url
string<uri>

LinkedIn company or school page URL. Must be exact format: https://www.linkedin.com/company/acme or https://www.linkedin.com/school/stanford-university

Example:

"https://www.linkedin.com/company/stripe"

Response

Radar created successfully

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