Deactivate multiple radars
Bulk
Bulk Deactivate Radars
Synchronously deactivate up to 500 radars in one request.
DELETE
Deactivate multiple radars
Bulk deactivation is synchronous: the response already contains the final
outcome for every requested ID. Its
The JSON body must contain only
bulk_id is a correlation value for logs;
it is not stored and cannot be used with the bulk-create status endpoint.
Each item is the same success or error response returned by
DELETE /v1/radars/{radar_id}, with only
bulk_id, item_index, and the requested radar_id added. A mixed request
still returns top-level HTTP 200; inspect each item’s code and the summary.radar_ids. Supply 1–500 unique UUIDs.
Malformed JSON, empty strings, invalid UUIDs, duplicate UUIDs, unknown fields,
or an empty/oversized array reject the whole request with 400 before any
radar changes.
Monthly radars enter their paid grace period. Update-based radars deactivate
immediately. Missing, unowned, or already inactive radars appear as item-level
failures without preventing other valid items from being deactivated.
Correlating items to your request
Every item carries a top-levelradar_id and item_index — on both
successful and failed items. Use these two fields for all bulk correlation,
regardless of outcome:
radar_id— the exact ID you requested for this item.item_index— the zero-based position of this item in yourradar_idsarray.
data is the unchanged single-DELETE resource
response, so data.radar_id repeats the same value. This duplication is
intentional: treat data as the returned radar resource, and the top-level
radar_id as the request correlation field.
On a failed item there is no data object, but the top-level radar_id is
still present — so you never have to branch on success vs. failure just to find
the identifier.
Always identify items through the top-level
radar_id and item_index. Treat
data.radar_id as part of the radar resource, not as the correlation key.Authorizations
Body
application/json
Required array length:
1 - 500 elementsResponse
Bulk deactivation completed, including any item-level failures
Available options:
completed Available options:
200 Correlation ID for this synchronous request; it is not persisted for polling.
- Option 1
- Option 2