hosting

POST `/v1/sites/{siteId}/offsite/restore`

Overwrite the site from a copy held in the customer's own storage.

Authentication

Send an API key as a bearer token. The key must carry the hosting.backup.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/offsite/restore \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "copy_id": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Destructive: the site's current files and database are replaced. Each archive is decrypted and its HMAC verified before the restore can use a byte of it; a copy altered at the destination is refused. Incremental copies restore with every archive they depend on. Requires hosting.backup.manage.

Parameters

Name	Type	Required	What it is
`siteId (path)`	`Uuid`	Yes	Site ID (UUIDv7).

Request body

Name	Type	Required	What it is
`copy_id`	`string`	Yes	—

Response

Name	Type	Required	What it is
`workflow_id`	`string`	Yes	—
`state`	`SiteOffsite`	Yes	—

Errors this endpoint can return

401 · 403 · 404 · 422 · 503

POST /v1/sites/{siteId}/offsite/restore