Backups & snapshots

A snapshot is a point-in-time capture of a site — its database and files together. You take a snapshot with a backup, restore one in place, and read a per-site rollup across your whole account at GET /v1/backups/status. Snapshots are how you roll back data, where a deployment rollback rolls back code.

The snapshot object

Field	Type	Description
id	string	Stable identifier, e.g. snap_01J8....
site_id	string	The site this snapshot was taken from.
taken_at	string	RFC 3339 timestamp of the capture.
size_bytes	integer	Size of the snapshot.
tags	string	How the snapshot came to be, e.g. scheduled vs on-demand.
synced_at	string	When the snapshot was last synced to off-host storage.
retention_reason	string | null	Why the snapshot is being kept beyond the normal window, if it is.

List snapshots

GET /v1/sites/{siteID}/snapshots

backups:read List a site’s snapshots, cursor-paginated.

List a site's snapshots

curl "https://api.managed.dev/v1/sites/site_01J7.../snapshots?limit=20" \
  -H "Authorization: Bearer mfk_live_..."

Response

{
  "data": [
    {
      "id": "snap_01J8...",
      "site_id": "site_01J7...",
      "taken_at": "2026-06-24T03:00:11Z",
      "size_bytes": 412300544,
      "tags": "scheduled",
      "synced_at": "2026-06-24T03:12:40Z",
      "retention_reason": null
    }
  ],
  "pagination": { "next_cursor": "eyJ0...", "has_more": true },
  "request_id": "req_01J9..."
}

Take a backup

POST /v1/sites/{siteID}/backup

backups:write Take a snapshot now. Returns a 202 job (type backup.create); the new snapshot_id is on the job’s result when it succeeds.

cURL

Take a snapshot before a risky change

curl -X POST https://api.managed.dev/v1/sites/site_01J7.../backup \
  -H "Authorization: Bearer mfk_live_..." \
  -H "Idempotency-Key: 3f8c...b1"

Go

Take a snapshot and wait for it

job, err := client.Backups.Create(ctx, "site_01J7...")
if err != nil { return err }
done, err := client.Jobs.WaitSuccess(ctx, job.ID, nil)
// done.Result["snapshot_id"] identifies the new snapshot

mf CLI

Take a snapshot before a risky change

mf backups create --site site_01J7... --wait

Response (202 Accepted)

{
  "data": {
    "id": "job_01J9...",
    "type": "backup.create",
    "status": "queued",
    "progress": 0,
    "created_at": "2026-06-24T14:50:33Z",
    "resource": { "type": "backup", "id": "site_01J7...", "site_id": "site_01J7..." },
    "result": null,
    "error": null,
    "links": { "self": "/v1/jobs/job_01J9...", "stream": "/v1/jobs/job_01J9.../stream" }
  },
  "request_id": "req_01J9..."
}

Restore a snapshot

POST /v1/sites/{siteID}/snapshots/{snapID}/restore

backups:write Restore a snapshot in place, replacing the site’s current database and files. Returns a 202 job (type backup.restore).

cURL

Restore a snapshot

curl -X POST https://api.managed.dev/v1/sites/site_01J7.../snapshots/snap_01J8.../restore \
  -H "Authorization: Bearer mfk_live_..." \
  -H "Idempotency-Key: a90d...5e"

Go

Restore a snapshot

job, err := client.Backups.RestoreSnapshot(ctx, "site_01J7...", "snap_01J8...")

mf CLI

Restore a snapshot

mf backups restore snap_01J8... --site site_01J7... --yes --wait

Restores are anchored to the database snapshot

The database snapshot is the restore anchor: a restore rebuilds the site to the generation that database capture belongs to, so database and files come back as a consistent pair rather than a mix of points in time.

Restore is destructive

A restore overwrites the site’s current database and files. Take a fresh backup first if there’s any chance you’ll want the current state back.

Account-wide backup status

GET /v1/backups/status

backups:read A cross-site rollup: for every site you own, the latest snapshot’s age and size plus the status of the last backup job. One call answers “is everything backed up?” — for a dashboard or a nightly check. truncated is true when your owned-site set exceeded the per-request cap.

cURL

Check backup health across the account

curl https://api.managed.dev/v1/backups/status \
  -H "Authorization: Bearer mfk_live_..."

Go

Check backup health across the account

status, err := client.Backups.Status(ctx)

mf CLI

Check backup health across the account

mf backups status

Response

{
  "data": {
    "truncated": false,
    "sites": [
      {
        "site_id": "site_01J7...",
        "slug": "acme-store",
        "domain": "acme-store.com",
        "latest_snapshot_at": "2026-06-24T03:00:11Z",
        "snapshot_age_seconds": 42600,
        "size_bytes": 412300544,
        "last_backup_status": "succeeded"
      }
    ]
  },
  "request_id": "req_01J9..."
}

Next steps

Snapshots & backupsThe conceptual walkthrough — automatic schedules, pre-push backups, and one-click restore.

DeploymentsRoll back code with a deployment rollback; roll back data with a snapshot restore.

Async jobsTrack the 202 jobs that backup and restore return.