Changelog
Back to All
Added

BackupRadar API – Retire Unused Backups

October 1st, 2026

Summary

This release adds a second write endpoint to the BackupRadar API: you can now retire backups programmatically. POST /backup-radar/v3/backups/retire retires every backup that matches the filters you supply — by job name, device, client, or how long it has been since a result was last received — and records the reason you provide against each retired backup and in the retire activity log.

Every request can be previewed first: set dry_run to true to see the full match set without retiring anything. A live request returns the same shape, listing the backups that were retired.

There are no breaking changes to existing endpoints.

Changes

Backups

  • POST /backup-radar/v3/backups/retire
    • N/A → Available
    • Type: addition
    • Notes: Retires backups that match the supplied filters. reason is required, and at least one filter must be provided: job_name, device_name, client_name, client_id, device_id, or no_result_in (days since the last result, including backups that have never reported). Filters are exact, case-insensitive matches combined with AND. Set dry_run: true to preview the match set without retiring anything, and close_psa_tickets: true to also attempt to close related tickets in the connected PSA. The response reports match_count, retired_count, and the matched or retired backups in data; the full set is returned and is not paginated. Tenant-level API keys are accepted; a user-tied key must belong to a tenant administrator or a user with the Retire Backup permission, otherwise the request returns 403.

Dates

  • Effective: 2026-09-30