Skip to main content
DELETE
Deactivate multiple radars
Bulk deactivation is synchronous: the response already contains the final outcome for every requested ID. Its 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.
The JSON body must contain only 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-level radar_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 your radar_ids array.
On a successful item, 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.
This endpoint accepts a JSON body on a DELETE request. Some generated SDKs, older HTTP clients, and proxies silently drop DELETE bodies — if radar_ids arrives empty you’ll get a 400. Verify your client preserves DELETE bodies before relying on it in production. (curl, modern fetch, and Python requests do.)

Authorizations

x-api-key
string
header
required

Body

application/json
radar_ids
string<uuid>[]
required
Required array length: 1 - 500 elements

Response

Bulk deactivation completed, including any item-level failures

status
enum<string>
required
Available options:
completed
code
enum<integer>
required
Available options:
200
message
string
required
timestamp
string<date-time>
required
bulk_id
string<uuid>
required

Correlation ID for this synchronous request; it is not persisted for polling.

summary
object
required
radars
object[]
required