hosting

PUT /v1/sites/{siteId}/external-backup

Connect an externally hosted site so we can back it up.

Alle hosting-eindpunten

Authenticatie

Stuur een API-sleutel mee als bearer token. De sleutel moet over de permissie hosting.backup.manage beschikken; een sleutel zonder deze permissie wordt geweigerd met een 403 in plaats van een 404.

Dit eindpunt vereist geen organisatie-id. Uw sleutel identificeert al de organisatie waartoe deze behoort, en het antwoord is hierop afgestemd.

Probeer het

Vervang alles tussen punthaakjes door uw eigen waarden en de sleutelplaatsvervanger door een sleutel uit uw dashboard.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/external-backup \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "channel": <ExternalBackupChannel> }'

Ingelogd? De API-console in je dashboard vult je echte organisatie-id en je eigen sleutel in, en voert het verzoek uit tegen de live API zodat je de daadwerkelijke respons kunt zien. Open dit eindpunt in de API-console

Details

Configures one of two channels. `connector` — the customer installs the Zinn® Connector plugin and pairs it. Nothing else is needed and we never hold a server credential. The plugin makes outbound calls only; it opens no route on their site. Backup only: it cannot restore. `ssh` — the customer gives us a host, a username, the document root and a private key. This channel can also **push a site back**, including when the site itself will not load, which is the only way a one-click restore can be honest. `ssh_secret` is write-only. It goes straight to our secret store and only a pointer to it is kept; it is never returned by this or any other endpoint. Re-connecting a `connector` site mints a fresh pairing token and invalidates whatever the previous install held. Requires `hosting.backup.manage`.

Parameters

NaamTypeVerplichtWat dit is
siteId (path)UuidJaSite ID (UUIDv7).

Aanvraaglichaam

NaamTypeVerplichtWat dit is
channelExternalBackupChannelJaHow we reach a site we do not host. `connector` is the Zinn® Connector plugin (outbound-only, backup but no restore); `ssh` is SSH/SFTP, the only channel that can push a site ba…
ssh_hoststringNeeRequired when `channel` is `ssh`.
ssh_portintegerNee
ssh_usernamestringNeeRequired when `channel` is `ssh`.
remote_pathstringNeeThe document root, required when `channel` is `ssh`. Refused at configuration time rather than at 03:00 when the sweep runs.
ssh_secretstringNeeThe private key (PEM) or password. Written to our secret store and never returned. Omit it to keep the credential already stored.

Reactie

NaamTypeVerplichtWat dit is
configuredbooleanJaFalse when nobody has connected this site yet. The rest of the object is still present and empty — a screen must not have to tell "not set up" from "failed to load" by the absen…
channelExternalBackupChannel | string<>JaEmpty string when `configured` is false.
enabledbooleanJaA disabled connection is paused, not deleted — the set-up survives.
can_restorebooleanJaWhether we can push a backup back down this channel. **False for `connector`**, and that is not a limitation to route around: a WordPress plugin cannot run inside a WordPress to…
summarystringJaOne sentence stating what this connection can and cannot do, composed server-side so every surface says the same thing about the backup/restore asymmetry.
ssh_hoststringJaEmpty on a `connector` connection.
ssh_portintegerJa
ssh_usernamestringJa
remote_pathstringJaThe site's document root — what we archive, and what we restore into.
credential_presentbooleanJaWhether a credential is stored in our secret store. The credential itself is never returned by any endpoint.
last_verified_atstringJaNull when the connection has never been checked.
last_verified_okbooleanJaNull means never checked, which is not the same as failing — the absence of a measurement is not a measurement.
last_verify_detailstringJa

Fouten die dit eindpunt kan retourneren

401 · 403 · 404 · 422