> ## 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.

# Changelog

> Product updates and API improvements.

<Update
  label="August 18, 2026"
  description="More precise job-title filtering"
  tags={["API", "Radars", "Filtering"]}
  rss={{
title: "Build more precise job-title filters",
description: "Company radars now support full Boolean job-title expressions and exact whole-title matching."
}}
>
  ## 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](/guides/filtering-and-personas) and [Create Company Radar](/api-reference/create-company-radar).
</Update>

<Update
  label="August 17, 2026"
  description="Contact identifier validation improvements"
  tags={["API", "Radars", "Contacts"]}
  rss={{
title: "More reliable contact identifiers and duplicate errors",
description: "Contact job-change radars now reject shared inboxes and non-person LinkedIn URLs, and duplicate responses identify the matching field."
}}
>
  ## 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](/api-reference/create-contact-radar) and [Error Handling](/guides/error-handling).
</Update>

<Update
  label="August 16, 2026"
  description="Synchronous bulk radar deactivation"
  tags={["API", "Radars", "Bulk"]}
  rss={{
title: "Deactivate up to 500 radars in one request",
description: "The new bulk DELETE endpoint returns an ordered final outcome for every requested radar."
}}
>
  ## 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](/api-reference/delete-bulk-radars).
</Update>

<Update
  label="August 14, 2026"
  description="Radar creation improvements"
  tags={["API", "Radars"]}
  rss={{
title: "Choose how far back a new radar should scan with updates_since",
description: "New radars can now include an updates_since timestamp to control the source-event boundary for initial processing."
}}
>
  ## 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](/quickstart), [Getting Started](/getting-started), and [Bulk Create](/guides/bulk-create-guide).
</Update>