Sign in
Backups

Paginated run history for a backup schedule (one row per scheduler tick).

Changed on

Returns one [ScheduleRunSummary] per scheduler tick, with child backup counts aggregated in a single SQL round-trip. Legacy backups rows (pre- fan-out) are surfaced as synthetic single-job runs so history does not disappear. Ordered by started_at DESC (newest first).

Use GET /backups/schedule-runs/{run_id}/jobs to drill into a single run.

get/backups/schedules/{id}/runs

Request

  • Base URL: /api (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /api/backups/schedules/{id}/runs
  • Auth: HTTP bearer

Path parameters

idinteger required

Query parameters

pageinteger

Page number (1-based, defaults to 1, clamped to 1 if < 1).

page_sizeinteger

Items per page (defaults to 20, clamped to 100 if > 100).

Response

Paginated run history for the schedule

pageinteger required

Current page (1-based).

page_sizeinteger required

Number of items per page.

totalinteger required

Total number of run entries across all pages.

Changes

  • 4b228ebed583Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

  • 1dc3e6788214Revision changes
    • warning

      removed the optional property from the response with the status

    • warning

      removed the optional property from the response with the status

    • warning

      removed the optional property from the response with the status

    • warning

      removed the optional property from the response with the status