BackupRadar API – Backup Results Ingestion

Summary

This release introduces the first write endpoint in the BackupRadar API: you can now push backup results into Backup Radar programmatically. POST /backup-radar/v3/backups accepts a batch of backup entries — each identifying a device, job, and client — with results for backups, replications, verifications, boot verifications, and alerts.

It also improves device-name filtering on the devices endpoint: devices that are not mapped to a ScalePad device are now matched by their Backup Radar device name instead of being excluded from filtered results.

There are no breaking changes to existing endpoints.

Changes

Backups

• POST /backup-radar/v3/backups
  • N/A → Available
  • Type: addition
  • Notes: Ingests backup results in batches. Send a JSON array of entries, each identifying a device, job, and client, with one or more result collections (backups, replications, verifications, boot_verifications, alerts); each result carries a time and a status of success, warning, or failure. A batch is all-or-nothing — if any entry fails validation the entire request is rejected — and may contain at most 10,000 results across all collections. A successful request returns an empty 202 Accepted; accepted results are processed asynchronously.

Devices

• GET /backup-radar/v3/clients/devices
  • Unmapped devices excluded from filtered results → matched on br_device_name
  • Type: change
  • Notes: filter[device_name] now also matches devices that are not mapped to a ScalePad device, using their Backup Radar device name (br_device_name); previously these devices were excluded whenever the filter was applied. Filtering still prefers the ScalePad device name when a mapping exists. Filtered results may now include devices they previously omitted.

Dates

• Effective: 2026-08-18