List backup schedules
Each schedule has its next three runs in UTC. The first target gets a daily schedule at 02:00 UTC with the tiers core and logs, that keeps 14 archives and 30 days.
GET
/api/v1/console-backup/schedulesAuthorization
tse_sessionAPI key · cookierequiredResponses
200
OK
schedulesBackupScheduleItem[]requiredShow propertiesHide properties
Array of
BackupScheduleItemcreated_atstring<date-time>requiredcronstringrequiredA cron expression of 5 fields (minute hour day-of-month month day-of-week), in UTC
enabledbooleanrequiredidstringrequiredkeep_countinteger<int64>requiredThe retention keeps the newest archives of the schedule on its target. 0: no count limit
max_age_daysinteger<int64>requiredThe retention deletes the archives of the schedule that are older. 0: no age limit
next_runsstring<date-time>[]requiredThe next three runs, in UTC. Empty when the schedule is off
target_idstringrequiredtiersstring[]requiredupdated_atstring<date-time>requireddefault
Error
codestringStable code of the refusal, when the route has codes
detailsstring[]Additional detail, e.g. per-field validation failures
errorstringrequiredHuman-readable error message