Skip to main content
POST
Set updates_since to include past activity. Add it inside each applicable item in radars (not at the request root), a few weeks or months back, to get eligible activity from that date plus ongoing updates. Without it, most radars start at their exact creation time (not the start of today), so even a post from a minute earlier is excluded and your first check may be empty. Updates can take time to arrive.New hires and promotions use UTC calendar months: an earlier month includes activity from that month on. Without updates_since, they start in the month the radar was created.
The bulk_completed webhook carries the full per-item result array. At 1,000 items with rich custom_fields or filter data, the payload can approach 1–2 MB — ensure your receiver can handle it. Alternatively, use GET /v1/radars/bulk/{bulk_id} to fetch results on demand.
countries and rounds on industry items are checked like Create Industry Radar: us is saved as United States. An item with an unsupported or repeated value, or with a filter its radar type doesn’t use, fails on its own; the request still returns 202.

Set a priority for your bulks

Use priority to decide which of your bulks runs first. For example, mark an urgent customer list "high" so it doesn’t wait behind a large backfill, or mark the backfill "low". Add a top-level priority: "low", "normal" (default) or "high". Other values, including null, return 400. Priority applies to the whole bulk, can’t be changed later, and is returned by the 202 response and Get Bulk Create Status. It is separate from any priority you put in custom_fields, which is only echoed back. Your items are picked in this order:
  1. Remaining items of bulks that have already started, oldest first.
  2. Bulks that haven’t started: high, then normal, then low, oldest first within each.
Priority changes the order of your bulks, not their speed. Bulks run in parallel, so finish order isn’t guaranteed.

Authorizations

x-api-key
string
header
required

Body

application/json
radars
object[]
required

Array of radar payloads. Each item uses the same body structure as single radar creation (POST /v1/radars): include radar_type plus the matching fields for that radar (for example domain/profile_url/keyword, filters, custom_fields). Item-level validation runs asynchronously after the request is accepted.

Required array length: 1 - 1000 elements
priority
enum<string>
default:normal

Orders your bulks: remaining items of started bulks go first, then high, normal, low. Set once at submission. Other values and null return 400.

Available options:
low,
normal,
high
Example:

"high"

webhook_url
string<uri>

Optional webhook endpoint that receives async item results and the final bulk_completed event. Omit for poll-only mode and track the batch via GET /v1/radars/bulk/{bulk_id}. Omit the field entirely to disable webhooks — an explicit null is rejected with 400.

Maximum string length: 2048
Example:

"https://your-domain.com/webhooks/tamradar"

Response

Bulk submission accepted and queued for async processing

status
enum<string>
required
Available options:
success
code
enum<integer>
required
Available options:
202
message
string
required
bulk_id
string<uuid>
required
priority
enum<string>
required

Effective priority set at submission; normal when omitted.

Available options:
low,
normal,
high
summary
object
required
timestamp
string<date-time>
required