Bulk
Get Bulk Create Status
Poll async bulk submission status and per-item outcomes.
GET
Get async bulk submission status
How bulk status works
After submitting a bulk request, the response transitions through two states:processing— At least one item is still being created.summary.processingshows how many are in flight.completed— All items have reached a final processing state (createdorfailed). Optional webhook-related fields may still appear on items later.
status = "completed". If you provided a webhook_url, you can also listen for the bulk_completed webhook, but poll this endpoint to confirm completion even if individual webhook deliveries fail. For webhookless (poll-only) submissions, this endpoint is the tracking surface for every outcome, including failures.
Bulk priority
The top-levelpriority is "low", "normal" or "high", as set at submission.
Bulks submitted without one, including older bulks, return "normal". See
Set a priority for your bulks.
radars[] follows your submitted item order, not the order items finish in.
Per-item fields
Each submitted item appears inradars[]. While it is running, the item contains
only its index, custom fields, and processing status. Once it settles, the item
contains its update_id and update_type, plus either the created radar under
data or the item-level error fields. Use status to tell running, created and
failed items apart.
Optional webhook-related fields. After an item’s webhook is delivered, the
item may also include
record_id, bulk_id and completed_at. Items with
status "success" may also include code (201) and message; items with
status "error" may also include discovered_at. Don’t rely on these fields
when polling.
Items are always returned ordered by item_index.
Response
Bulk status retrieved successfully