Skip to main content
​
APIRadarsFiltering
More precise job-title filtering

​
Build more precise job-title filters

Company radar job_titles filters now support:
  • Combining required groups with AND, such as ("sales operations") AND (manager OR VP).
  • Standalone and grouped exclusions with NOT.
  • EXACT("Sales Operations Manager") for case-insensitive, normalized whole-title equality.
  • Nested expressions with standard NOT, AND, then OR precedence.
Existing filters remain compatible. Quoted phrases continue to use containment, while EXACT("...") is optional new syntax for whole-title matching.Malformed expressions return an actionable job_titles error. Bulk submissions remain asynchronous, with malformed expressions recorded as item-level failures.See Filtering and Personas and Create Company Radar.
​
APIRadarsContacts
Contact identifier validation improvements

​
Contact radar validation changes

New contact_job_changes radar requests now:
  • Reject role-based, shared, and placeholder email addresses.
  • Accept only LinkedIn person profiles under /in/; company, school, and legacy /pub/ URLs are rejected.
  • Report duplicate matches as identifiers.email or identifiers.profile_url in 409 responses.
These changes apply to new single and bulk radar creation requests. Existing radars are unaffected.See Create Contact Radar and Error Handling.
​
APIRadarsBulk
Synchronous bulk radar deactivation

​
Bulk deactivate radars

​
Features

  • Send 1–500 unique radar IDs to DELETE /v1/radars/bulk.
  • Receive final ordered success or failure details for every ID in one synchronous response.
  • Reuse the same per-item success and error contract as single-radar deactivation.

​
Behavior

  • Monthly radars enter their paid grace period; update-based radars deactivate immediately.
  • Expected item failures do not prevent valid items from being deactivated.
  • Bulk create and bulk delete share the bulk rate-limit budget.
See Bulk Deactivate Radars.
​
APIRadars
Radar creation improvements

​
Set a radar start point with updates_since

​
Features

  • Create company, contact, industry, and bulk radars with an optional updates_since timestamp.
  • Make matching source events at or after that timestamp eligible for delivery.
  • Inspect the stored setting in radar responses as a normalized UTC timestamp or null.

​
Compatibility

  • include_historical remains accepted, but updates_since is the field to use for new integrations.
  • Historical results may continue arriving during the first 24 hours after radar creation.
See Quickstart, Getting Started, and Bulk Create.