Skip to main content
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.processing shows how many are in flight.
  • completed — All items have reached a terminal state (created or failed). No more changes.
Poll this endpoint until status = "completed", or — if you provided a webhook_url — wait for the bulk_completed webhook instead. For webhookless (poll-only) submissions, this endpoint is the tracking surface for every outcome, including failures.

Per-item fields

Each submitted item appears in radars[]. While it is running, the item contains only its index, custom fields, and processing status. Once it settles, the item contains either the created radar under data or the item-level error fields. Webhook correlation fields may also appear after webhook processing enriches the stored item payload. Items are always returned ordered by item_index.
Re-fetch until the top-level status is "completed". The radars[] array includes all submitted items from the start; in-flight stubs are replaced by their success or failure fields as processing completes.

Authorizations

x-api-key
string
header
required

Path Parameters

bulk_id
string<uuid>
required

Bulk submission ID returned by POST /v1/radars/bulk

Response

Bulk status retrieved successfully

status
enum<string>
required
Available options:
processing,
completed
code
enum<integer>
required
Available options:
200
message
string
required
timestamp
string<date-time>
required
bulk_id
string<uuid>
required
summary
object
required
radars
object[]
required