Set a priority for your bulks
Bulk submissions now take an optionalpriority: "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
priorityvalue other thanlow,normalorhigh, includingnull, now returns400. Before, it was ignored.
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.usorUnited States. See Supported Countries.rounds: only rounds of the listed types, e.g.SeedorSeries A, spelled exactly as in Round Types.
Behavior changes
countriesonindustry_funding_roundsradars now filters deliveries. Before, it was saved but not applied.- A
Seedfilter does not include rounds labeledUnknown; addUnknownto receive them. An unknown or repeated round label returns400. countriesis accepted only onindustry_job_openingsandindustry_funding_rounds, androundsonly onindustry_funding_rounds. Sending either on another industry radar type now returns400. In bulk creation, that item fails and the request still returns202.
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_hiresfor now; more radar types will follow. limitis 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
limitis only for previews. Create Company Radar, Create Contact Radar and Create Industry Radar now return400when the body includeslimit. Bulk creation and legacyPOST /v1/radarsare unchanged.
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_countandcountry. ip_geo: the visitor’s approximatecity,stateandcountry.usage: the charge for this lookup and your remaining balance.
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
limitto request 1–500 radars per page; the default remains 50. - When
has_moreistrue, passnext_cursorback as thecursorquery parameter. - Use
created_sincewith an ISO 8601 timestamp and timezone to include radars created at or after that time. countis the number of radars on the current page, not a total count.
Behavior changes
- The maximum
limitis now 500. Higher values return400. - Unknown query parameters now return
400instead of being ignored. This catches mistakes such as sendingnext_cursoras the parameter name instead ofcursor. radar_status=inactivenow includes every radar that is not active.
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.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_sincetimestamp (or radar creation time if not set) as the cutoff for eligible posts. To receive historic or backdated activity, setupdates_sinceto the earliest date you care about.
Build more precise job-title filters
Company radarjob_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, thenORprecedence.
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.Contact radar validation changes
Newcontact_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.emailoridentifiers.profile_urlin409responses.
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.
Set a radar start point with updates_since
Features
- Create company, contact, industry, and bulk radars with an optional
updates_sincetimestamp. - 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_historicalremains accepted, butupdates_sinceis the field to use for new integrations.- Historical results may continue arriving during the first 24 hours after radar creation.