Skip to main content
APIRadars
Set a priority for your bulks

Set a priority for your bulks

Bulk submissions now take an optional priority: "low", "normal" (default) or "high". Mark an urgent customer list "high" so it doesn’t wait behind a large backfill. Bulks already started still go first. Responses now include priority (older bulks show "normal").

Behavior changes

  • Any priority value other than low, normal or high, including null, now returns 400. Before, it was ignored.
See Bulk Create Radars.
APIRadarsFunding Rounds
Filter funding radars by country and round

Filter funding radars by country and round

Industry funding rounds radars can now be limited to the funding rounds you care about. Rounds that don’t match are not delivered and not charged.
  • countries: only rounds whose company is headquartered in one of the listed countries (company.hq_country). Up to 5; send codes or names, e.g. us or United States. See Supported Countries.
  • rounds: only rounds of the listed types, e.g. Seed or Series A, spelled exactly as in Round Types.
Any listed value matches within a filter. With both filters, a round must match one listed country and one listed round. Without filters, you keep receiving every round.

Behavior changes

  • countries on industry_funding_rounds radars now filters deliveries. Before, it was saved but not applied.
  • A Seed filter does not include rounds labeled Unknown; add Unknown to receive them. An unknown or repeated round label returns 400.
  • countries is accepted only on industry_job_openings and industry_funding_rounds, and rounds only on industry_funding_rounds. Sending either on another industry radar type now returns 400. In bulk creation, that item fails and the request still returns 202.
See Create Industry Radar and Industry Funding Rounds.
APIRadars
Preview a radar before you create it

Preview a radar before you create it

POST /v1/radars/preview takes the same body you would send to create that radar (Create Company, Contact or Industry Radar, by radar_type), plus an optional limit, and returns a few recent matches right away. Use it to check that your filters find the people you expect before you create the radar.
  • Available for company_new_hires for now; more radar types will follow.
  • limit is 1–100, default 3. Keep it low; higher limits are slower.
  • Each returned update is charged at your per-update rate, shown in usage.unit_price_usd. A preview that returns nothing is free.
  • Previews need an API key, an active account (not a trial) and per-update pricing for that radar type.
  • Send previews one after another rather than in bursts, and allow a client timeout of at least 35 seconds.

Behavior changes

  • limit is only for previews. Create Company Radar, Create Contact Radar and Create Industry Radar now return 400 when the body includes limit. Bulk creation and legacy POST /v1/radars are unchanged.
See Preview Radar.
APIWebsite Visitor Reveal
Identify the company behind a website visitor

Identify the company behind a website visitor

Website Visitor Reveal turns an anonymous visitor’s IP address into the company behind it, so you can route, score or follow up on visits from target accounts.POST /v1/company-reveal accepts one public IPv4 or IPv6 address and returns:
  • Matching companies with domain, name, profile_url (LinkedIn), industry, employees_count and country.
  • ip_geo: the visitor’s approximate city, state and country.
  • usage: the charge for this lookup and your remaining balance.
Lookups that find a company are charged; lookups without a match are free. Each request is a new lookup, so store results on your side instead of repeating them. Requests count toward your account’s write rate limit. Website Visitor Reveal is enabled per API key; contact us to enable it.Coming soon: a website pixel that identifies visiting companies automatically, without building your own IP capture, following in the coming weeks.See the Website Visitor Reveal guide and Reveal Company.
APIRadarsPagination
Easier radar reconciliation with cursor pagination

Easier radar reconciliation

You can now page through your radars and more easily reconcile the inventory in your system with TAMradar after an interrupted sync, missed creation response, or integration incident. Follow the cursor through every page to complete the traversal. If radars may have been created while you were paging, start a fresh request without a cursor to pick them up.GET /v1/radars now returns radars in deterministic newest-first pages:
  • Use limit to request 1–500 radars per page; the default remains 50.
  • When has_more is true, pass next_cursor back as the cursor query parameter.
  • Use created_since with an ISO 8601 timestamp and timezone to include radars created at or after that time.
  • count is the number of radars on the current page, not a total count.

Behavior changes

  • The maximum limit is now 500. Higher values return 400.
  • Unknown query parameters now return 400 instead of being ignored. This catches mistakes such as sending next_cursor as the parameter name instead of cursor.
  • radar_status=inactive now includes every radar that is not active.
Keep all filters unchanged while following a cursor. To discover radars created during a traversal, start a fresh request without a cursor. created_since filters creation time only, not later status or configuration changes.This endpoint returns radar records. Use GET /v1/updates to retrieve radar findings and failures.See List Radars.
APIWebhooksSocial Engagements
Social engagement monitoring window extended to 5 days

Social engagement monitoring window extended to 5 days

contact_social_engagements and company_social_engagements radars now:
  • Monitor each post for up to 5 days for net-new engagement activity (previously 48 hours)
  • Per-post engagement cap raised from 200 to unlimited — all engagements within the 5-day window are captured
  • Use your updates_since timestamp (or radar creation time if not set) as the cutoff for eligible posts. To receive historic or backdated activity, set updates_since to the earliest date you care about.
See Contact Social Engagements and Company Social Engagements.
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.